Bolt memory: knowledge that persists, context that resets
Bolt draws a clean line: project knowledge is background that persists, and context is working memory with a size limit that clears. Most project decisions arrive as context and leave the same way.
StackBlitz. Sources checked 2026-09-25.
How Bolt handles memory today
Bolt documents two memory types. Project knowledge holds goals, core features, and design principles, is stored outside the active chat, and is not cleared when you reset context. The context window tracks recent messages, uploaded files, and project files, with a size limit that you manage by resetting.
That model is honest and effective for one project at a time. It is scoped to the project in Bolt and to the person using it.
What Bolt forgets
Resetting context is a feature. It is also a deletion.
- Working context you cleared, including the reasoning from the last hour of building.
- Project knowledge when you start a new project, which is the point, and also the cost.
- Anything from your editor, terminal, or another assistant.
- Team continuity, since knowledge is per project and per user.
The fix with MemoryRouter
Keep building in Bolt, and keep the decisions in a vault your other tools can read. Exported code lands in an editor with hooks or MCP, and the memory should land with it.
- 1
Connect the tools that continue the work
Once the project outgrows the browser, Claude Code or Codex keeps building. Install the hook package in the repository so the context follows the code.
Install in the exported repo
npx -y memoryrouter-claude init - 2
Write the durable facts once
Architecture decisions, service choices, and constraints belong in memory. Project knowledge in Bolt stays short and instructional.
Keep the project memory when the project leaves the browser. 14-day free trial.
Related
Bolt memory FAQ
Sources
Sources checked 2026-09-25. Tool behavior changes; check the vendor docs before relying on a detail.