Problem: 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 conversat…

Thank you for sharing this in so much detail :pray: We’ll share with the v0 team for their thoughts! I don’t think v0 loses context of the chat as it’s essentially a duplicated chat though, right?

+1 I want to go back to the old workflow: edit → verify → manually push → sync to GitHub not auto-sync on every single change. How to disable automatic GitHub syncing in v0

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 previ…

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.

As they say, if there’s nothing wrong with it don’t touch it!

Correct. Nothing to add. @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.

Cross-posting this mostly for completion :slight_smile: [image] v0 @v0 Our GitHub integration just got a major upgrade: • Every code change generates a commit • Open PRs and merge directly from chat • New in-chat GitHub panel to connect, see sync status, branches and commits. • Improve…

I see this is being addressed, but just adding a +1. I stepped away for a few days, and these updates and new workflow cut me at the knees.

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 wi…

Disabling the forced branch-per-chat workflow in v0 for iterative development

pawlean (Pauline P. Narvas) January 26, 2026, 5:23pm 7

Hey folks!

The v0 team shared that we have a UX improvement coming out soon that will let you continue working in the same chat even when you merge PRs.

Bring back the pull/publish workflow in v0

Topic		Replies	Views
Best practices for creating a new v0 chat using a different GitHub branch v0 v0 , v0-ui	9	237	January 29, 2026
v0 GitHub integration PR failures and branch management issues v0 v0 , v0-agent , v0-ui	2	49	March 6, 2026
GitHub "Create Repository" in v0 Question (v0 GitHub Beta feature) v0 v0	2	94	June 6, 2025
Bidirectional git sync for v0 Premium users is now in beta Announcements v0	25	2564	October 14, 2025
v0 project chats reverting to default branch instead of selected base branch v0 v0 , v0-ui	1	16	April 6, 2026

Disabling the forced branch-per-chat workflow in v0 for iterative development

Related topics