skip to content

v0

Vercel's v0 turns prompts, screenshots or Figma frames into Next.js apps with Tailwind and shadcn/ui, previews them in a sandbox VM and deploys to Vercel. Asked for what the output still lacks.

part ofAI coding toolsread it →
on this pageshow

explore

questions

6

In a v0 chat connected to GitHub, which branches does v0 create and push to, and what happens to them when you publish?

level: middleimportance: must knowfreq 9%

answer

  1. never straight to the base
  2. created lazily, on the first change
  3. every change is a commit
  4. Publish creates or reuses, then merges
  5. next change, next branch

basics

~20 s

A GitHub-connected v0 chat starts from a base branch; its first code change creates a working branch that gets every change as an automatic commit. Publish merges that branch's pull request into the base, and the next change starts a new working branch.

solid answer

~40 s

Each chat starts from a **base branch** — the branch it checks out and its pull request targets. v0 creates a **working branch** lazily, when the chat first has a code change to push (named like `v0/main-abc123`), and commits and pushes every generated change there automatically; it never pushes straight to the base branch. Each working branch gets its own Vercel preview deployment, and the branch menu shows the preview, diff, pull request and CI checks, with **Pull Changes** to bring new base-branch commits in. **Publish** creates or reuses the pull request, merges it into the base branch and waits for the production deployment. The chat then returns to the updated base branch, and the next code change starts a new working branch in the same chat.

go deeper

for a junior

Recall the rule: v0 works on its own working branch, never the base branch, and Publish goes through a pull request.

for a middle

Walk the lifecycle: lazy working branch, automatic commits, per-branch preview, Publish creating or reusing the pull request and merging it, then a fresh working branch.

for a senior

Use the branch menu to keep a long chat healthy — Pull Changes for base-branch drift, Fix CI or Fix Conflicts, Duplicate for a parallel direction — and know the repository becomes the source of truth.

for a principal

Decide how v0 chats map onto the team's branching model: which base branches chats may target, and how many parallel chats one repository can absorb.

## Why the branch model matters When a v0 project is connected to GitHub, the repository becomes the **source of truth** for the code — the GitHub page warns that deleting the repository may make the code unrecoverable. Every generated change therefore lands in Git, and the branch model decides what a reviewer sees and when anything reaches the branch production builds from. The current automatic flow arrived with the v0 update the FAQ dates **February 4, 2026**, which replaced manual commits and branch management. ## The four branches | Branch | Role in v0 | |---|---| | **Default branch** | The repository's default on GitHub; v0 selects it initially at import unless you choose another | | **Base branch** | The branch a chat starts from and the branch its pull request **targets** | | **Working branch** | Created by v0 for the chat; receives every generated change instead of the base branch | | **Production branch** | Set on the linked Vercel project; it produces production deployments, while other branches produce previews | The base branch is often the production branch, but it is chosen per chat; the Vercel project's production branch stays responsible for production deployments. ## The life of one chat 1. **Start.** Connecting (Project menu → Settings → GitHub) creates a private repository and pushes the code; **Import from GitHub** instead checks the repository out at the selected base branch in the chat's sandbox. 2. **First code change.** v0 creates the working branch lazily — only when it has a change to push — with a name like `v0/main-abc123`. 3. **Every later change.** Committed and pushed automatically. Each push updates that branch's own **preview deployment**, so the app can be reviewed without touching the production URL. 4. **Publish.** v0 creates a pull request if the branch has none or reuses the existing one, **merges it into the base branch**, and waits for the production deployment. 5. **After publishing.** The chat returns to the updated base branch; the **next code change creates a new working branch** and a new preview. No new chat is needed. v0 never pushes directly to the base branch; the FAQ puts it as "v0 never pushes directly to `main`". ## The branch menu The current branch sits next to **Publish** in the chat header, and its menu gathers the Git workflow: - **Preview deployment** for the working branch and its URL; - **Branch and diff** — open the branch on GitHub, see additions and deletions; - **Pull request** — create one or open the existing one; - **CI checks** — running, passing, skipped or failing; - **Pull Changes** — bring commits from the base branch into the working branch; enabled only when the base branch has commits the chat lacks, and conflicts are resolved first with **Fix Conflicts**; - a v0 action that follows the branch state: **Review Code**, **Fix Build**, **Fix CI**, **Fix Conflicts** or **Fix CI + Conflicts**. ## Parallel work - A **new chat** is a separate stream of work: it starts from its own base branch and creates its own working branch, sharing the repository and Vercel project. - **Duplicate…** in the chat menu opens the **Duplicate Branch** dialog, which creates a new chat and branch holding the current branch's commits, targeting the same base branch. - Importing the same repository again creates another chat, not another repository. - Teammates working in their own editors push to the same repository; once their work is on the base branch, **Pull Changes** brings it into the chat's working branch. ## What this does not decide The flow guarantees that v0's changes arrive on a branch and through a pull request. Whether that pull request needs a human approval or passing checks before Publish can merge it is decided by the repository's own GitHub rules, which v0 follows; how those rules work belongs to the GitHub material on pull requests and branch protection. ## Common misreadings - **"v0 holds my changes until Publish."** No — every code change is already a commit on the working branch, visible on GitHub and built as a preview. - **"Publish just opens a pull request."** Publish also **merges** it into the base branch when the repository's rules allow, then waits for production. - **"A published chat is finished."** The chat continues; the next change opens a new working branch from the updated base. - **"Anyone on the team can open the chat."** By default, team members need access to the repository on GitHub to collaborate on its chat and generate previews; the workspace setting **Allow v0 to Act on Behalf of Members** lets members without a GitHub connection on their Vercel account use the workspace's GitHub integration instead.

  • In v0's branch menu, Pull Changes is greyed out. What does that tell you?
    **Pull Changes** is enabled only when the base branch has commits the chat does not, so a disabled button usually means there is nothing new to bring in. If the pull request has merge conflicts, they must be resolved first — the branch menu offers **Fix Conflicts** for that.
  • Two people want to explore different directions on the same v0 project at once. How?
    Use separate chats on the same project: each starts from its base branch and creates its own working branch and preview, sharing the repository and Vercel project. To branch off work already in progress, use **Duplicate…** in the chat menu, which creates a new chat and branch holding the current branch's commits.
  • Why does an imported repository's v0 chat show no preview at first?
    The working branch, and with it the working-branch preview, is created only when the chat first changes code. The base branch may already power production, so v0 waits for a code change; send a prompt that edits the project and wait for the automatic push and deployment.

  • v0 commits generated changes straight to main
  • You must start a new chat after every publish
  • Changes stay local in v0 until you click Publish
  • Pull Changes pushes the working branch into the base branch
  • v0 creates the working branch the moment you import a repository

Assumes v0's docs as fetched on 2026-10-04; the automatic working-branch flow arrived with the v0 update the FAQ dates February 4, 2026.

open as a page

When you ask v0 for a web app without naming a stack, what does it generate, and how reliable is it with another framework?

level: juniorimportance: should knowfreq 6%

basics

~20 s

v0 defaults to a Next.js app written in React and TypeScript, styled with Tailwind CSS and built from shadcn/ui components. It can use other frameworks, but its docs say Next.js gives the most reliable results.

open as a page

In v0, a team wants no change to reach production without a teammate's approval. What actually holds back a Publish, and where are the gaps?

level: seniorimportance: should knowfreq 5%

basics

~20 s

v0's Publish merges the chat's pull request itself, so a teammate's review happens only if the repository requires one on the base branch. Projects without GitHub deploy straight to Vercel, and v0 roles decide who may publish.

open as a page

In v0, each VM-backed chat runs in a Vercel Sandbox. What does that sandbox isolate, and what can code running inside it still reach?

level: seniorimportance: should knowfreq 4%

basics

~20 s

A v0 sandbox isolates each chat from other chats, other users and production. Inside it, code can reach the internet (Sandbox Network Policy defaults to allow-all) and the project's Development environment variables, which any terminal process can read.

open as a page

In v0's Design mode, what happens to your visual tweaks when you click Apply, and where is Design mode unavailable?

level: middleimportance: nice to knowfreq 4%

basics

~20 s

Design mode tweaks stay pending until Apply sends them to the chat, where v0 generates a new, revertable chat version with the change in source code. It works only on a chat's latest version, on the latest preview runtime.

open as a page

When a designer pastes a Figma link into v0 to build a dashboard, what does v0 read, and when is a frame link better?

level: middleimportance: nice to knowfreq 3%

basics

~20 s

v0 reads a Figma file's design data — frames and their images, variables and styles, auto layout, exact text, assets, component names and Dev Mode links. A frame link matches one exact screen; a file link suits a whole flow.

open as a page