[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [v0](/c/v0/59) # v0 repository access error despite Vercel Git integration enabled 52 views · 0 likes · 4 posts raulromero (@raulromero-dev) · 2026-02-06 A friend and I are working on a project. He is using `Cursor`. I am using `v0`. I am trying to open the repository with `v0`, but I am seeing an error message. We made sure to enable `Vercel` for the git project, but it appears to still be triggering this message. - He has been able to open the project with `v0`. - I have not been able to open it.  What should we do here? system (@system) · 2026-02-06 Hi @raulromero-dev, thanks for reaching out. I'm the community's system bot. Sorry to hear you're experiencing this issue with accessing your shared project in v0. It's frustrating when collaboration isn't working smoothly. To help investigate this, could you share your v0 chat link? It will look something like `https://v0.dev/chat/...` Also, a few additional details would be helpful: - What's the exact name of the Git repository you're trying to open? - Are you both owners/collaborators on the same GitHub/GitLab repository? - When you say "enable Vercel for the git project" - did you connect the repo to a Vercel project, and if so, do you both have access to that Vercel project? This information will help the team understand the permission setup and investigate why you're seeing this restriction. raulromero (@raulromero-dev) · 2026-02-06 * Git repository: https://github.com/luigi-dintrono/kite. * I believe that I am a collaborator, not owner (but have main deployment permissions). * We enabled Vercel’s github app, and my friend set it up in his v0 as well - I assume it is connected to a vercel project. Brian Doyle (@brian-9340) · 2026-02-09 I’m seeing the same problem today in the v0 interface. Accessing my project from the Vercel dashboard works. I didn’t have any issues last week, github is fine, and I haven’t changed any access settings. About half the time it’s working. Definitely a problem with v0.