Hi there.

I’ve searched and found this error reported multiple times, often for different reasons, and I’ve noticed that the suggested fixes vary depending on the case.

Context

• I'm on a pro subscription
• This project has been built entirely inside v0 over a sustained period
• It includes a large number of .tsx files, App Router pages, and assistant-generated scaffolding
• The assistant has been used continuously to build, edit, and refactor the full app structure

What’s Going Wrong

• Any new prompt is blocked, even when it contains only a short instruction
• Starting a new chat within the same project results in the assistant saying it cannot access known files (e.g., app/page.tsx)
• I haven’t tried forking individual components because I'm working on full app-level changes (e.g. fixing files, renaming, restructuring)
• I'm also currently blocked from completing a working Git deploy due to build errors that can’t be addressed while this messaging issue persists

Assumptions

• The assistant context for the current chat may have grown too large from extended use
• The error may stem from a memory limit rather than actual prompt length
• New chats appear disconnected from the file system, even when launched from the same project

What I'm Hoping to Resolve

• Is there a way to reset or clear chat context without losing the project’s file structure?
• Can assistant access be restored to a project when new chats fail to recognise existing files?
• Are there known limits or best practices for managing long-running v0 projects?