have you duplicated the main chat as well?

So then your second branch in gh is also connected to a duplicate chat. Then you can push all update to that branch. merge to main when ready, and then pull in merged changes to you rmain chat.

Hi,

I ended up deleting/creating/adding a new git repo 3 times and it worked the third time

Thanks for your help!

Alright…

So it worked for awhile then decided no more. It insists now that I do a preview mode on a new git branch before I can put anything to production. When I try to put it to production, it does not deploy to my domain, but a temp vercel domain. I do not want this. v0 should not be creating branches on my behalf/publishing to a branch that I have not it set to publish to. Furthermore, when I go to manually try to push the changes to the main git branch and then publish it on v0 and then it goes right back to the “new” git branch that was created. Is there anyway someone can look into this issue on my account? I am paying for a team plan.

and you have checked that all the auto commit / pull settings are turned off? Have you tried unlinking the branch and then relink to a new one maybe?

Really weird honestly as I have never had this happen where when I deploy it auto creates a new Git branch. maybe its a setting you have set somewhere in Vercel specifically on that project by chance?

I know this may sound like a dumb question, but have you tried asking the v0 agent why this is happening? I mean…maybe its worth a shot? Just a thought, but honestly not sure. All so odd.

Hoping someone else from the community or Team will see this later or Monday and be able to hop in.

Hey Sean ,

I actually did ask the agent for help regarding the github and it said that was outside of it’s scope and to reach out to support.

Yes, I checked that all the auto commit/pull settings are turned off. Yes, I tried unlinking the branch and then relink to a new one, I created 3 new repositories, does that count?

I have also having been issues getting my Supabase to connect, it tries to create a new account every time I’m prompted to install/connect Supabase (even though it’s already been installed) the variables are all in place in v0 and vercel. “Install Supabase” is the agents response to a LOT and it’s frustrating bc it is installed and the variables on both vercel and v0 are correct. Even on the supabase account it has that little vercel triangle indicating it’s connected.

I really hope to get to the bottom of all this as it’s become really hard to create anything without these two things in place.

I would love the opportunity to have someone to take a look at my account and try to solve these issues, as I am a paying customer.

See my attached moments of Supabase frustration below. I also made it a rule that “Install Supabase” cannot be the answer, that did nothing. I’m not sure what I am doing wrong when it comes to integrating these third-party tools.

Hmmmm ok yeah this is VERY odd for sure. Random question, what agent are you using? I dont think the solve to this will be the answer to what you say here, but I am just curious.

As for what could be happening, again, this is very weird and odd that it keeps repeating. Even when you have disconnected and reconnected.

I would say to try just starting fresh (import your code from github), but I understand that may not be a route you want to try. More just to try for more trouble shooting.

As for having someone from the Team look into this, I fully agree with you. I think with Holidays upon us, their response time may be a bit delayed. But I am certain they will see this and respond asap (I of course understand the frustration in the waiting though).

In the meantime, I want to see if some others from the community may have some ideas. @ussaaron ,@avik-creator, @hasriza any ideas here?

Hey Sean,

Thanks for getting back to me!

I use the v0 pro agent, I’ve tried the v0 max and it didn’t seem to make a difference. It just doesn’t seem to listen to me anymore, in the sense I ask it to do a very simple task and I’m ignored/nothing happens. I also keep getting “page unresponsive” when I’m on the v0 page for editing and the AI is thinking. I really am at a loss, but I cannot keep purchasing credits if it’s not going to operate.

I did recently transfer this project over from one account to another on v0. I did this so my v0/vercel accounts would both be on the same accounts, but should/would that have cause an issue? They should be on the same team accounts right? This is the only thing that I can think of that has changed.

There is clearly a bigger issue going on here and I don’t think I’m going to be able to solve it on my own, so I appreciate your response and for reaching out to your team members.

Happy Holidays!

@hutchisonmallory-557 If you click on the GitHub icon in the top right, what do you see? For example, here's what I see:

So it is creating a new branch on github everytime he deploys it?

Hello, that is what I see as well.

However, I am experiencing a recurring issue with the v0 GitHub integration where the tool is preventing me from deploying directly to my main branch.

Even when I have main set as my active branch in both the v0 and GitHub, attempting to 'Publish' or 'Push' triggers a forced redirect to a 'Preview Environment.' This automatically creates a new feature branch (e.g., v0-all-changes) and switches my active working branch to this new one.

If I manually switch back to main, v0 insists on a test environment deployment again or re-deployment to the production environment, which automatically puts git back to the “newly created” branch and traps me in a loop where it deploys to a "Preview URL" vs my "Production URL." I would like to restore the ability to push/deploy directly from my primary branch to production as I was able to do previously. Is there a project-level setting or a way to disable this forced branching behavior?

@hutchisonmallory-557 So you have selected “Production” and it's still deploying to preview? That sounds like a bug to me, hopefully the team can help you resolve this!

(You've selected “Production” in the publish menu?)

That is correct. I select “Production” and it deploys to a Preview URL even though I have a Production URL set to my account.

However, It will deploy to production if it is not Synced to GitHub, but as soon as the sync is active, the loop begins. I am using Vercel under ‘Project Settings’ to initiate the initial connection/sync with my Git account, and it appears correctly in my v0 dashboard shortly after, so the connection itself seems valid.

The branching issues have made deployment very hard. Even more concerning, the AI isn’t answering to simple tasks, I’m getting ‘Page Non-Responsive’ errors when trying to run queries, and I’m told by the AI (on repeat) that my Supabase integration is not installed, even though it has been fully integrated. I’m wondering if this is a larger infrastructure issue.

If you all could look into this, I would truly appreciate it!

Yeah. I cant replicate this issue at all. I have actually tried to haha. And all my deploys work fine and dont create new gh branches. Not sure what is going on tbh.

I’m happy to keep building in v0 without Git for now and will export the code manually until things are settled. My main priority has shifted to getting supabase connected so I can keep building. I’ve been running the logic manually in the Supabase dashboard, but to get the level of functionality we’re after, I need to link the environments directly. As you can see below, my Supabase project is already present; however, when selected, I get the red error message.

you may want to look into this wich @ussaaron posted. could be helpful https://community.vercel.com/t/v0-supabase-auth-installation-prompt/17270

Vercel Community

V0 Supabase Auth Installation Prompt

V0 Supabase Auth Installation Prompt You can paste this prompt directly into your V0 prompt to have V0 fully install Supabase login with Supabase's latest...

Hi Sean,

I’ve successfully connected Supabase and moved away from Git. However, I’ve hit a deployment 'split-brain' issue: while my frontend changes go live instantly when I hit publish, the backend/API logic is not deploying.

I have tried clearing the cache and redeploying on my own, and it has done nothing. I've also verified the live setup by changing a visual on the main page - that update works, but the backend seems to remain stuck on stale code (see snips below. Please note: the edits it made to try to fix this issue did not work).

Since I am no longer using Git to trigger builds, what is the best way to force a full rebuild of the backend so the server-side logic matches the frontend since the deploy button doesn’t work? Also, has anyone on your team been able to look further into the ongoing Git issue? It would be great to return to a standard workflow!

hmmm ok this is definitely a head scratcher. I am not sure what is going on here to be honest nor the best way forward. I want to try asking two others. @ussaaron from the community I feel may have an idea and / or @jacobparis from the Team may have a solid solution right away or be able to help move this to the right person. If we dont hear anything in a day or two on this, I will reach out to the Team directly for you.

Sorry for delays on this and understandable frustrations.

I could probably solve this pretty quick if I could look at the actual code, but without that I'm only guessing. If there are sync issues between your v0 project and github or Supabase there are a few troubleshooting steps to try first. First check if you can execute sql actions directly through the sql editor in the supabass dashboard, you want to rule out RLS rules that may be triggering silent errors. Next you want to rule out v0 fork issues so duplicate your chat, and try again from v0. If that fails the next thing I would do is start a whole new v0 project and try to recreate your current environment.

Also you can check for logging errors by opening console log and going to the network tab and checking the response body of your requests. I've debugged a lot of v0 issues this way because the response errors are usually more verbose when accessed through the network tab.

@hutchisonmallory-557 have you been able to try what Aaron mentioned above or connect with him to maybe have him take a look at the code?

Hi @heystu, I was not able to solve the issue.

✓ I can execute sql actions directly through the sql editor in my supabass dashboard.

I have tried forking; however, when I try to fork, the SQL scripts refuse to run. I believe this is due to the CSP error below. Gemini seems to think the issues lies in my middleware file. However, when I manually made the suggested Gemini edits, and requested the AI do it, nothing changed.

For some reason when I fork, a new v0 project is created… Not sure what I’m doing wrong there?

If @ussaaron would be able to connect or has any recommendations specific to the v0 console errors below, I would appreciate it!

@hutchisonmallory-557 I have reached out to the team now regarding this issue. Hoping they will be able to jump in with some answers and solutions for you here. Sorry for any inconvenience you are experiencing due to this issue.

Thanks for bringing this to our attention, @heystu!

@hutchisonmallory-557 The team had a look. Can you let us know if it happens again?

Hi Pauline P. Narvas,

This issue continues to occur. Although I’m beginning to wonder if this is not related to my code, as I the same issues show up when I have trouble deleting my forks, which now show up as projects on my account.

Actually, I’m just now realizing that my project on v0 is gone. They are all forks now, I’m not sure where went/when it disappeared. Also, when I go to supabase, and go to the dropdown they are all forks listed. Shouldn’t they be the projects?? I could be wrong here! Perhaps this is why it doesn’t want to connect?

Vercel is displaying all my forks as new projects as well.

Perhaps I do not understand what a fork is. I would like to clarify that the “New Chat” is what we call a fork and it should not create new projects on vercel/v0 each time it is selected?

Hmmm interesting. I have never used the “new chat” in the version history as a way to fork. I have always just duplicated (what used to be called fork in v0), and thus have never had this issue. but if youre using “new chat” from the version / chat history, I wonder if this is the culprit behind it all. It seems like we may be getting closer to the problem at had. Lets see what they team comes back with and / or if you can try another method (duplicate rather than new chat) to fork and see if that works. Just more trouble shooting I think, but I feel we are getting there.

Hi @heystu

Could I verify where the following API keys are located on supabase? I’m currently using the same two keys to verify the following 4 keys. I’m wondering if this could be the issue? Also, I have switched to “duplicating” vs “new chat.” This hasn’t helped with the supabase issue so far, as I still get the SCP and API errors in my console log, but I will stick to this proper method in hopes that it might clean up the process.

NEXT_PUBLIC_SUPABASE_ANON_KEY

SUPABASE_ANON_KEY

NEXT_PUBLIC_SUPABASE_SERVICE_ROLE_KEY

SUPABASE_SERVICE_ROLE_KEY

The following keys are on supabase are being used for all four areas, as I’m unsure what is supposed to be for the NEXT_PUBLIC_SUPABASE_SERVICE_ROLE_KEY and NEXT_PUBLIC_SUPABASE_ANON_KEY.

Hi guys! @ussaaron @pawlean @heystu @bestcodes

This past month all credits have gone towards account diagnostic/feedback (I have spent $20 today and am already being prompted to to purchase more).

Unfortunately, I like to eat and cannot afford this.

While we were able to get git and supabase connected, it still appears that v0 cannot execute SQL commands on supabase and v0’s AI still struggles to complete very simple tasks.

• AI 5 edits in: “I’ll add a debugging tool…. (even though one was already added the second edit in)” Like no, fix the problem dude lol.

I will most likely be switching to a new product by the next billing period. Do you all have any recommendations as fellow developers?

Thank you!

Hi @hutchisonmallory-557 , really sorry to hear this. Of course this is not what we in the community or team want to happen. I fully understand your frustration and feelings on this. I’m going ping the Team right now and see what can be done to solve this and maybe more.

Hang in there with us.

Hi @hutchisonmallory-557, I apologize for the delay our team is looking into it. I'll share here once I have an update for you.

I admit we are getting places, so thanks everyone for your help and for looking into this.

Here is where we are at:

✅Supabase is now connected.

✅Git is now connected.

✅v0 is able to publish without creating a new branch each time.

😔v0 won’t let me “Run Files.”

😔Every time I try to fork (even doing it the correct way) the AI starts acting funny/messing up my work. I always have to go back to my old chat.

😔v0 is unable to use AI efficiently. It’s very hard to complete a simple task and takes many prompts. That said, there are almost 800 prompts on this one chat as I cannot fork/run the files.

😔v0 is unable to execute commands to supabase and lies that is does.

It is my understanding that v0 is over here trying to create RLS polices on supabase and is indeed charging for it; however, to my knowledge this is not possible. AI has instructed me to go try to click all 40 scripts and go run them manually myself, but when I “click” them, they won’t open. Also, that sounds like a real pain lol.

Hi guys,

I’m just wondering what is going on, on your end???

Supabase is now connected.

Git is now connected.

v0 is able to publish without creating a new branch each time.

Those “Run Files” appear to be gone.

I’m able to fork now using the new git functionality.

Buuuuttttttt

I cannot get my v0 page to load for the life of me. It is “Page Unresponsive” or just a blank page. I have cleared my cache/browser history. I have upgraded to 1g fiber internet. I have tried a new browser. It only happens on the v0 page.

At one point I did get v0 to briefly load; however, the AI wasn’t displaying the edits it was saying it was making.

I have tried submitting a support ticket via v0 but the AI doesn’t give you an actual “submit” button after the view case form. If you you all could escalate this info, it would be appreciated.

Hi @pawlean do you know if the team ever found a solution for this specific case?

It's difficult to see what the issue is from this long thread.

What exactly are you seeing now?

Hi Pauline P. Narvas,

I’m following up because the platform's performance isn't just unstable—it's regressing. Rather than improving with updates, my experience is getting worse, and I am now completely blocked:

• Access Blocked: I am currently getting an "unauthorized" error when trying to create a new branch from my projects page, despite being logged into the correct profile. I can no longer access the editor at all.

• AI Logic Failure (Ghost Edits): When I recently had access to the chat, the AI became a liability. It would claim to have applied fixes, but no changes were reflected. Worse, when it did make changes, they were often incorrect or broke existing functionality, making the application worse instead of better.

I’m a huge fan of v0's potential, but it has reached a state where it is actively hindering my progress rather than helping.

Could you please look into why my account is hitting this "unauthorized" wall? I'm happy to provide my Project ID to help resolve this.

Update to my last post: The 'Access Blocked' issue has resolved itself, which is great.

However, I'm still hitting the AI Logic Failure (Ghost Edits) which has broken some existing functionality. I'm trying to roll back to a version from before the Git changes were implemented to start fresh, but I'm stuck—I can publish the old version live on Vercel, but I can't seem to get that version back into the v0 editor.

Any advice on how to force v0 to 'revert' to a specific previous deployment/state?

Currently, the 'healthy' version of my project is live on both GitHub and Vercel, but the v0 editor has diverged significantly. Over the last 190+ edits, the AI has essentially been 'fighting itself'—consuming my credits while introducing Ghost Edits that have broken existing functionality.

The Issue: v0 has locked the old chat that I want to fork or branch from because it’s a "merged" branch. It literally prevents new messages from being sent to protect the integrity of the main code.

I am actually dumbfounded by the behavior I'm seeing: if the code is deployed on Vercel/main, shouldn’t that be the version reflected in the Git main branch? When I attempt to create a new project using that same Git/main source, it still inexplicably pulls the broken state instead of the actual code in the main repo.

I’ve tried to have the AI help me redeploy prior edits as a last resort, but it seems unable to 'reach back' and pull the clean code from my Vercel deployment into the current editor state.

The AI itself has admitted to this UI limitation:

'Unfortunately, v0's GitHub UI doesn't seem to have an obvious branch selector dropdown visible in this view... it doesn't appear to be clickable.’ and 'There’s no obvious in-app way to switch branches like you’d expect’

The Goal: I need to force the v0 editor to sync back to the state of my last successful Vercel deployment or my GitHub main branch from my functional baseline.

Since the correct code exists externally, is there a way for your team to manually 're-index' or 'reset' the v0 project state to match the Git/Vercel? I'd like to stop burning credits trying to fix 'ghosts' and just get back to a functional baseline. Two Questions:

1. Is there a formal v0 support line that I am unaware of for issues involving credit loss due to tool failure?

2. Can your team manually force the v0 editor to 'reset' or re-sync to match a Deployment ID?

I need to get back to a functional baseline without burning more credits on a UI that won't let me roll back to my basline.

Hi @anshumanb, @heystu, @pawlean, @ussaaron, and @bestcodes—I know Mercury is in retrograde, which is usually my go-to explanation for everything from IT glitches to relationship issues, but I’m hitting a wall that’s becoming a real blocker for my work.

I’m struggling to roll back to a previously synced branch. Despite having a healthy, functional version live on Vercel/GitHub, my current v0 project has diverged significantly. I’m caught in a forward-only loop of edits that are breaking existing functionality and burning through my team credits.

To make matters worse, the Branch/Version selector widget seems to have vanished from my UI, so I can't steer the project back to the correct state. As a paying team member, I’m finding it difficult to reconcile this forward-only behavior with the workflow I need to maintain my project.

Could someone please point me toward a solution? I really want to stick with you all, but I’m currently stuck fighting an editor that won’t let me revert or sync with what is currently published. What am I missing with this new Git update? Any direct assistance would be huge.

First question, have you tried starting a new chat / project (as in start from home menu or choose “new chat”) and just import your github since you have a function version on there?

Second question: Is the project you are having issues with, with the new or old v0? Im assuming new since you no longer see the github branch menu. That is “gone” in the new v0. I say “gone”, because its not “really” gone, its just new and different. When you duplicate branches to start a new one all of your branched chats (which branch in github) will show in your project (see image). Those “recent chats” are just my duplicated chat / branches which coincide with github, although they have been merged of course).

You can also check your github connection status, commits, etc in Settings now (see image)

Hi, thank you so much for getting back to me. I’ve tried creating a new project by importing from Git, but it still pulls the broken version, which is why I’m at a loss.

I’m not a Git expert, but here is my confusion: since my code is correctly deployed on Vercel and Git shows no pending changes/nothing to compare, I should be seeing the functional version. Instead, v0 seems to be serving an outdated snapshot.

Regarding the old chats, they seem to have 'archived' themselves—they are now merged with the main branch and no longer allow me to branch off or revert to a specific state. It’s like the history is being locked in a 'forward-only' state.

Am I missing a setting, or is the new v0 environment failing to sync with the actual repository state? How do I switch to the correct branch on v0? Could you walk me through the steps to 'un-merge' or effectively re-branch from those previous states? Or, if they are permanently merged, is there a way to force a new branch from a specific commit in my GitHub history so I can bypass this 'forward-only' lock? Honestly, I do not want to have to create a new project everytime I need to go back a version.

Below:

I have successfully promoted this version on Vercel, and it is live on my production site. I assumed that this promotion would also reflect in my Git main branch—am I mistaken about that workflow?

Furthermore, if this version is verified on my live site, why would v0 not reflect this state? If v0 is supposed to be linked to my Git main branch, why is it serving an outdated version? The old branch that I want that is active on Vercel:

Old chats do not allow me to back-track or use the work from that branch; instead, they just pull the current work of the lastest version that is non-functional:

Since this chat / thread has been goign on since December, I think it would be good for you to share your chat link so the team can possibly look at it. It seems there are some issues going on.

To help debug your v0 project, could you share your v0 chat link? It looks like https://v0.app/chat/... — you can copy it from your browser’s address bar while in the chat.

You’ll also need to unlist the chat so our team can view it — here’s how: https://v0.app/docs/sharing

v0.app

Sharing | v0 Docs

Share your v0 chat with others to showcase your prompt history or to collaborate on generating components. This allows for seamless teamwork and feedback.

This helps the team reproduce what you’re seeing much faster. Thanks!

I have unlisted the chat link below for your team to review.

Here is the link to the branch I am currently working from/was bracnhed off from the version I am trying to get back to. Please note, the functionality within this version does not match that of verison main-19. I need the version that was successfully merged, and have included a screenshot of that functional version within the chat itself. The merged version does not give me the power to share, otherwise I would.

Update, I learned how to edit on Git and force pulled the old edits. Please let me know if there is an easier way to get old merged branches pushed, as this took me a second to learn, thanks!

were you able to figure this out yet? If not, can you add the chat link so maybe someone from the team can take a closer look.

if you can share a chat link just remember it looks like https://v0.app/chat/... — you can copy it from your browser’s address bar while in the chat.

You’ll also need to unlist the chat so the team can view it — here’s how: https://v0.app/docs/sharing

v0.app

Sharing | v0 Docs

Share your v0 chat with others to showcase your prompt history or to collaborate on generating components. This allows for seamless teamwork and feedback.

This helps the team reproduce what you’re seeing much faster. Thanks!