The Bolt.new
Emergency Rescue Manual

The Problem: Bolt tries to fix a bug, fails, and repeats the same wrong code until your tokens are gone. This is the #1 cause of token waste in Bolt.new.

The Solution:

• Type /reset in the chat input
• Or manually delete the node_modules reference
• This clears the agent's hallucination without losing code
• Re-prompt with a simpler, focused request

The Problem: The app is crashed, but the LLM is still "thinking" and charging you. Hidden processes keep burning tokens even when nothing is working.

The Solution:

• Check the Terminal tab for hidden infinite loops
• If the build indicator is red, STOP immediately
• Don't ask it to "fix" anything yet
• Manually revert the last file change first

The Problem: "Failed to persist chat messages" errors. Work gets lost, conversations reset, and you have to start over.

The Solution:

• Exit Incognito or private browsing mode
• Disconnect VPN temporarily
• Switch to a standard browser profile
• Allow cookies from bolt.new domain

The Problem: Large codebases cause AI to "forget" the core architecture. Simple errors go unfixed because the AI lost context.

The Solution:

• Copy your core App.tsx (or main entry)
• Copy your package.json
• Start a fresh Bolt thread
• Paste them as "Context Only" to reset memory window

The Problem: Deployments fail due to GitHub token or repo permission mismatches. Code won't sync, builds break.

The Solution:

• Verify Repository Secret in GitHub settings
• Check it matches the VITE_ variable in Bolt dashboard
• Confirm environment variables are set in both places
• Re-sync tokens if permissions changed

The Problem: Missing packages like vue-router or pinia cause mysterious crashes. Builds fail with cryptic errors.

The Solution:

• Check package.json imports match installed deps
• Run: npm install vue-router@4 pinia@2 --save
• Use exact versions, not "latest"
• Clear node_modules and reinstall if needed