Original Summary

I'm building Blabee with my cofounder. In July, the project centered on restoring shared ChatGPT conversations and exploring their concepts and conversation flow in a web app. Our August planning doc described a much broader ambition: connect conversations, GitHub, Notion, and calendar data, understand someone's work, and suggest what to do next. The same document also had an explicit "excluded from the MVP" list: Understanding an entire Notion workspace Figuring out priorities from a calendar General-purpose screen analysis and a large project dashboard Team approval workflows, a mobile app, and voice commands Supporting every coding agent from the start These were things we chose to leave outside the initial scope, not completed features we removed. The moment we chose to focus on was much smaller: a coding task finishes or needs a decision, and the person chooses what happens next. The priority list put Codex first, with another coding-agent integration later. That became the focus for our small Mac interface: show the result and Codex's suggestions, then pass the person's choice back to the same conversation. Codex supplies the suggestions; Blabee handles the interface and the return path. The larger idea stayed in the plan. What changed was the size of the first interaction we wanted to build and check. Looking back through those notes, the exclusion list makes that decision much clearer than just saying "we simplified the MVP." What did you leave out of your first version even though it felt central to the bigger idea? Current status: the Mac build is ready to try. Request access at https://biadone.com/blabee and we'll send you the build.   submitted by   /u/Biadone_Blabase [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/27 20:05:17