vO project stuck on restore checkpoint - needs a branch to continue

Help
1
## Problem

My v0 project “Spyford SecureOps Ecosystem” is stuck.
The project displays “Needs a branch to continue”, but branch creation always fails.
The workspace repeatedly reloads from the same restore checkpoint and does not persist new files, commits, or dependencies.
Eventually the chat reports that the sandbox is pinned to an old restore checkpoint, so every rebuild is discarded.

Steps to reproduce

  1. Open the existing v0 project.
  2. Click Continue.
  3. v0 requests a branch.
  4. Branch creation fails or the project shows “Load failed”.
  5. Reloading or restoring versions does not fix the problem.

What I already tried

  • Creating new v0 chats
  • Creating new branches
  • Restoring previous versions
  • Reloading the project
  • Rebuilding multiple times
  • Contacting the v0 assistant
    Nothing resolves the issue.

Expected behavior

The project should create a working branch and persist new files so development can continue.

Actual behavior

The sandbox continually reloads from the same restore checkpoint and loses all new work.
Could someone from the v0 engineering team investigate whether this project is stuck on a broken restore checkpoint or branch state?

2

While a member of our team prepares to jump in, you might find your answer even faster in our community resources.

3

Hi Spyfordsecureops,

That sounds like the chat/project state is stuck before v0 can create or attach a usable working branch, especially since new files, commits, and dependencies are being discarded after reload.

I’d stop making new changes in that stuck chat until you confirm where the latest recoverable code lives, otherwise you may keep losing work to the same checkpoint.

A few things I’d check:

1. Is the project connected to GitHub?
2. If yes, does GitHub show a v0/... branch for this chat?
3. Are there any recent commits from v0 on that branch?
4. Does creating a brand-new chat from the same project create a new branch successfully?
5. Does duplicating the branch into a new project behave differently?

If GitHub has the latest branch/commits, I’d treat GitHub as the source of truth and continue from a fresh v0 chat/project connected to that repo. If GitHub does not have the latest work and the chat keeps reverting to the same checkpoint, then this likely needs Vercel/v0 support to inspect the chat/project state internally.

The useful details to share publicly would be the exact error text from the branch creation failure, whether the project is GitHub-connected, whether a v0/... branch exists in GitHub, and the timestamp of the failed branch creation. I would avoid posting private chat URLs, repo access tokens, or project/account IDs.