Hey @jacob-8441, welcome to the community!

Next to the New Chat button, there is a dropdown arrow, where you can select Import from GitHub.

@mayven thanks I’m not sure that is what I’m looking for though. I’m not trying to import a repo. I want to have a buy directional set up where Leo is connected to my repo can create branches actively so I’m not importing my repo. I’m connecting it to my repo. Can I do that?

@jacob-8441 you can indeed, when you go through the Import from GitHub flow, you can connect it to your existing repo.

Once connected, each new v0 chat creates a dedicated branch off main so you can make changes in isolation, then once ready you can open the PR from v0.

The Git panel accessed from the sidebar on the left gives you details on the Git connectiion

Thanks @mayven - unfortunately it appears I’m getting errors here.

Here I am going to connect, create a new project (in our v0 team account.)

it’s confusing to me why we are doing this setup…

More setup….

Ultimately after skipping those steps, I get here, with an error.

Next, I try to connect v0 to our vercel account directly (pre-exsiting vercel account) - I do not get those prompts, but more errors.

Any help would be appreciated.

• Jake

Thanks for the info and screenshots, that’s helpful.

Before this, did you have your project deployed to Vercel already, outside of v0?

@mayven not in this team account. But to be honest I’m not sure. This project I am creating in my screenshot is 100% new, I am choosing the ‘create new project’ option on the funnel.

Also, if I go to our older, existing vercel account, and hit the button to launch v0, I see the same thing:

So basically:

• If I use an older, existing project and launch the v0, I get an error
• If I use the new v0 team account, and create a new project, I get an error
• If I use the new v0 team account, and connect it to our older vercel account (and project) I get an error

It looks like the Git connection / import was successful, but the previews aren’t initialising successfully.

They look like different errors on the different chats, so it’s difficult to know the source of the errors without the full context. However, you can try the Fix with v0 button to see if it can help get them working.

@mayven Yes so thats’ the problem, I’m hesitant to ‘fix’ errors on our repo…since, in theory our repo works fine. Again, maybe I’m missing something here. My assumption is we can hook v0 up to our repo, have it cut a branch, do some excellent interfaces, and then have that pulled back in and integrated.

It feels like based on these errors, the repo has to be in some ‘v0’ format to function…in other word v0 is expecting a structure it can work in, which seems to go beyond just a repo connection..

I’m not really sure, just seems like this should be easier, or I’m just not doing this right…

@mayven here is one random example, but they are all similar, basically v0 is expecting, I believe some core structures in my repo, an so when it doesn’t find them, it errors out…

@mayven I think this may be the root of the problem or at least one of the problems:

This is a hard limitation of the v0 environment that I need to surface honestly.

**The v0 build pipeline requires the Next.js app root at the repository root (/).** The build system runs next dev / next build from /vercel/share/v0-project/ and expects next.config.mjs, package.json, tsconfig.json, and app/ to exist at that level. There is no way to configure it to target apps/web as the build root -- there is no Turborepo workspace support, no custom rootDir override, and no way to change the working directory of the build command.

Concretely, if I move everything under apps/web/:

• The dev server will fail because it won't find next.config.mjs at root
• package.json at root is what drives dependency installation -- a nested one won't be picked up
• The preview/deploy pipeline has no mechanism to cd apps/web && next build

It feels like v0 really expects a pretty strict environment to work in - I would assume more flexibility given its’ trying to work in ‘other peoples repos’ - but again maybe I am missing some fundamental point here…

Still working on this, trying now to create a branch that is ‘v0’ friendly but that is proving to be a huge challenge in and of itself….

I understand, thank you for sharing all the context and sorry to hear you’re experiencing some friction in this flow!

Do you have any v0 chat URLs you can share? I can pass this and your feedback to the v0 team.

If you try the flow again, does adjusting the root dir at this step help?

@mayven no it does not - we tried many different variations including this.

Thanks for confirming!

I’ll share this with the v0 team, I know they are working hard to reduce error rates and improve the experience, so your feedback is appreciated.

Hey @jacob-8441, the v0 team has let me know that this is a known limitation that they’re actively working on, and they still do typically expect a single app repository to show a preview.

They’ve advised that even if there are errors with running preview, you can still prompt to make changes and look at preview deployments.

If you’d like to share any chat URLs, so that the team can look into this specific case further, feel free

Hopefully some improvements soon, appreciate your understanding!