Feature Request: GitHub Import for v0 + v0-1.5-md API Access

v0
1

I’ve run into a limitation with v0 that’s blocking a smoother workflow.

Currently, to use v0 in a project, you need to start the actual project in v0. If you missed that step, your options are:

  1. Create a new git repo using v0, then manually copy all existing code over and push
  2. Use the v0 API instead, but that’s limited to v0-1.0-md rather than the more powerful v0-1.5-md (Claude 4) model that the v0.dev interface uses

*Feature requests😘

  • Allow v0 to import existing GitHub repositories (similar to how Vercel handles regular project imports)
  • Open up v0-1.5-md model access via the API

This would make v0 much more practical for existing projects and teams who discover v0 after they’ve already started development.

Has anyone else encountered this? Any workarounds I’m missing?

1 Like
3

Thanks for writing such a detailed use case. I’ve forwarded this feedback to our v0 team.

You can already access v0-1.5-md model using the API. We’ve it on our documentation.

Let me know if you face any issues.

4

Not in Cursor:

According to https://vercel.com/docs/v0/cursor, we are still stuck with v0-1.0 there.

1 Like