I’m running into an issue with one of my v0 projects. The chat has gotten pretty long and I’m definitely noticing a drop in response quality. I read online that it should be possible to fork a chat so you can start with a clean conversation while still keeping everything from the project intact, like the connected GitHub repo, environment variables, and other settings.
The problem is: I can’t find this “fork chat” option anywhere.
When I try creating a new chat inside the same project, it has no awareness of my other chats in that project. It feels completely disconnected, as if it’s a brand-new workspace rather than a continuation with the same underlying context.
I’m assuming I’m missing something obvious, but I can’t figure out what. How do you correctly fork or duplicate a chat while keeping all the repo connections and environment settings?
If you have it syncd to github, just duplicate the chat (this was called fork originally by they changed it), then open the github drop down and set it to “Active branch”
If you are wanting to keep the original as a main “prod” and just duplicate to create feature branches and all, that is also possible and then you can merge all back into your main. This is what I typically do. but if you want to literally just duplicate, then what I wrote /show above works and all GitHub and Envs are saved.
Sometimes I simply duplicate a chat and then continue working directly in the main fork, which makes the whole process really quick. I’ve now started doing this more regularly, and it works perfectly. Before this, I honestly thought the AI quality was dropping because my project was getting more complex, but it turns out the long chat history was the issue. With a duplicated chat, the responses stay consistently great, even as the project grows.
As feedback for the v0 team, it would be helpful to make this workflow more obvious. A clearer “Start a fresh chat with existing context and repo” option would have saved me some confusion. I also never received the “long chat” warning I read about, so showing token length or providing a more explicit indicator that context is getting heavy could help developers understand when to fork or duplicate a chat.
