Original Summary

i was building a product and kept running into the same annoying workflow: chatgpt for research. cursor for code. v0/lovable for ui. another tool for deployment. then back to chatgpt to explain what i had already built. the actual problem wasn't that any of these tools were bad. it was context switching . every time i moved to another tool, i had to explain the project again, copy files, paste errors, or recreate context. after doing this way too many times, we started building orbit around a pretty simple idea: what if the workspace just remembered what you were doing? instead of: research → copy → chatgpt → copy → coding tool → copy → deploy we wanted: intent → build → iterate → ship the current version lets us go from a prompt to a working react/next.js app while keeping the project context in the same workspace. for example: "build me a saas dashboard with next.js + supabase authentication" → scaffold → database/auth setup → ui → iterate on the same project → continue without starting a new chat every time it's still early and there are definetly things that break. but honestly, the interesting part for me isn't really the ai generating code. it's not having to restart the conversation with the ai every 10 minutes. i'm curious how other people are dealing with this. how are you currently handling context when you use multiple ai coding/building tools on the same project? do you just accept the tab-hopping, or have you found a workflow that actually solves it?   submitted by   /u/Bold_ocean [link]   [comments]

  • 情报分类：开源项目与落地
  • 分类依据：内容涉及项目实践、创业、副业或变现
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/19 18:58:35