After connecting a project to GitHub, v0 now forces this workflow:
Every chat creates a new branch automatically
Every prompt that changes code creates a commit
Merging the branch closes the chat permanently
To continue working, I have to start a new chat and lose all conversation context
This completely breaks iterative development. I can’t “vibe code” with the AI anymore - every merge forces me into a new chat where v0 has zero context about what we were building, what decisions were made, or what direction we were heading.
Expected behavior:
Option to push directly to main (like before)
OR option to continue working in the same chat after merge
OR at minimum, carry conversation context into the new branch/chat
Current workarounds (all bad):
Never merge (defeats the purpose of git integration)
Disconnect GitHub entirely (defeats the purpose of git integration)
Manually paste context into every new chat (tedious, error-prone)
Why this matters:
The whole point of v0 is rapid iteration with an AI that understands your project. Forcing a “new chat = new branch = lost context” loop destroys that value. I’m now spending more time re-explaining context than actually building.
Other projects I have that aren’t connected to GitHub work fine - I can keep iterating in the same chat indefinitely. The GitHub integration shouldn’t break this core workflow.
Request:
Add a setting to disable auto-branching or allow continued iteration after merge. Let users choose between “clean git history” and “continuous development flow.”
Will there be an option to keep the old workflow? The new system is really difficult to use in team environments. It makes working with an IDE alongside v0 much harder and creates a new GitHub branch for every chat, which bloats repositories, and on large projects slows Github down a TON.
The previous edit → verify → manually push → sync to GitHub workflow was simple, predictable, and worked extremely well. It would be great to have the option to continue using that approach, as there was never anything fundamentally wrong with it.
I agree with Eric. There was nothing fundamentally wrong with the old workflow. Out of any kind of upgrade that could have been made, this one was unnecessary and makes v0 feel impossible to use.
@pawlean v0 loses at least the methodical part of the context and the working history. For a follow-up task in a new chat (with a new branch) it analyzed the whole project and suggested improvements instead of continuing the working path.
Yup, +1
This change had some good ideas, but forcing it was a bad idea.
Also makes me think the context of my previous chat is gone and therefore makes my interactions with the AI model less aware of what is going on (let’s say I’m working on a problem and think it’s fixed, so I merge, but then with more testing, it isn’t fixed so I have to start a new branch without any of the chat history).
Bang on the money! Couldn’t have been addressed more clearly.
When new beta “improvements” are implemented, option for regression is critical. Preview is now completely broken, and Github branching has became more complicated, every change is automatically committed, and the ability to change branch per chat is restricted. Why?
Production is held back because of this, can’t wait until it’s fixed.
We’ll share with the v0 team for their thoughts!