V0: New Chats Start from Project's Source Code

V0Aug 28, 2026View original changelog

A new chat started inside a V0 project now begins from that project's actual source — whether a GitHub branch, a managed repository, or the production deployment — so V0 has the real codebase from the very first message. This resolves a long-standing complaint from users that new chats on existing projects ignored the project's source code.

Key Takeaways

New chats inside a project now start from the project's real source code, whether GitHub branch, managed repo, or production deployment.
This directly resolves a known user complaint documented in the Vercel Community forums about new chats ignoring existing project code.
V0 now has full codebase context from the first message in a new chat, rather than discovering it partway through.
The fix makes V0 more reliable for iterating on already-shipped apps, not just starting new greenfield projects.
It reduces the risk of generated changes conflicting with existing code that V0 previously wasn't aware of.
This pairs with V0's other August 28 changes (previews, AI Gateway) as part of a broader push to make ongoing app iteration more seamless.

Fixing a Long-Standing Gap

Users have complained in V0's community forums that "new chats on a project do not pick up the project's source code," effectively forcing a workaround for anyone trying to iterate on an already-bootstrapped app. V0's August 28 release addresses this directly: a new chat started inside a project now begins from that project's own source, whether that source is a connected GitHub branch, a V0-managed repository, or the current production deployment.

Why It Matters

Previously, starting a fresh chat inside an existing project could mean V0 didn't have full context on the current state of the codebase, leading to generated changes that conflicted with or ignored existing code. With this fix, every new chat in a project has the actual code from its first message, making it far more reliable to use V0 for ongoing iteration on live, already-shipped applications rather than only for greenfield builds.