I’m reporting a critical, persistent platform issue that is blocking development entirely. Below is a clear, factual summary of everything I have experienced.
1. Repeated branch creation failures
I have created 7+ new branches (fresh, duplicate, and renamed).
None of these branches behave reliably inside v0.
New branches often inherit broken state from previous ones instead of starting clean.
2. GitHub access desync (Critical)
I am the repository owner with full GitHub and Vercel access.
Team members also have valid GitHub permissions.
Inside v0, both I and team members see:
“You do not have access to ”
This occurs on:
Old branches
Duplicate branches
Newly created branches
This clearly indicates a stale or corrupted GitHub App permission state on the v0 side.
3. Team members locked out inside v0
Team members with full GitHub access:
Cannot open v0 chats
Cannot interact with the repository
Access works correctly on GitHub, but v0 denies access.
4. Authentication breaks on new / duplicate branches
Supabase authentication works on one branch but fails on others.
On new or duplicated branches:
Login never initializes
Infinite loading occurs
ENV variables are present and verified.
This shows branch-specific environment or preview auth desync inside v0.
5. Old branch is fully working — but PR button is missing
One old branch is fully functional:
App loads correctly
Features work as expected
However:
The PR button is not available in v0 for this branch
This prevents merging or continuing proper workflows
So even the “working” branch is effectively blocked.
6. Duplicate branches do not reset state
Creating duplicate branches does not guarantee isolation.
Permission, auth, and deployment issues often persist across duplicates.
7. PR & chat workflow unusable
v0 chats tied to certain branches fail to load.
PR creation intermittently errors out or is unavailable.
Switching branches does not consistently resolve issues.
8. Credits lost due to platform instability
Significant v0 credits were consumed attempting to debug issues that later proved to be platform-level, not code-related.
9. Issues began after platform instability window
These problems started after:
GitHub disconnect/reconnect
v0 sandbox instability
Early February Vercel/v0 incidents
Strong indication of corrupted internal state rather than misconfiguration.
Overall Impact
Development is completely blocked.
Branches cannot be trusted.
PR workflows are broken.
Team collaboration inside v0 is unusable.
v0 access does not reflect actual GitHub permissions.
Core Pattern Observed
Branches, permissions, auth, and PR availability appear to share a corrupted internal state inside v0 that cannot be resolved from the user side.
In our case, the previous v0 version was more stable. After the recent updates, we are seeing regressions in branch handling, PR availability, team access, and preview loading, which were not present before.
When team members (with full GitHub and Vercel access) try to open the project in v0, it does not load for them at all. They see “You do not have access” even though they are correctly added to the team. The same project and URL open normally for me as the owner. also in my account as a owner i also not able to do PR
I demand a refund - as I too am having massive issues, and burned an entire months worth of premium credit trying to get v0 figure out the sync issue. I pulled locally and pushed and deployed, but the branch never updated with commits except for yesterday - the day I PAID for a boilerplate - which that’s new.
Now I’ve invested time, have to upgrade yet again to not lose my work - and here v0 is sitting on my somewhat ready landing page - and I can’t even connect it to my GitHub proper? I’ve been Pro with Vercel for a couple years, and this is the absolute worst cash grab I’ve ever seen. You want to prototype up something to work on - that’s v0, and it’s great for getting design ideas out like that, but if there isn’t a major reimbursement for this, it’s going to hurt on the actual vercel side - as what’s the point? Wasted time and micro transactions when I can write in vs with an agent all day that doesn’t talk to me twice and call it a day.
I’m bitter angry as wasted time is wasted progress
You can request a refund in 