Roo Code memory: strong instructions, thin history
Roo Code is configurable to an unusual degree, including modes, rules, and instruction scopes. History is the part that still resets with each task.
Roo Code. Sources checked 2026-09-25.
How Roo Code handles memory today
Roo Code documents custom instructions at global and workspace level, with workspace rules overriding global ones, plus mode-specific behavior. The community Memory Bank pattern adds markdown files the agent maintains, which works when the agent keeps them current.
Roo Code supports MCP servers, so external memory tools are a supported extension point rather than a hack.
What Roo Code forgets
Instructions scale with your patience. Memory should not.
- Task history at the end of a task, unless it was written into a bank file.
- Retrieval precision. Flat files are read whole or missed, so the bank gets big and expensive at the same time it gets stale.
- Cross-tool and cross-project continuity.
- Anything decided in a different mode, if the mode’s rules did not capture it.
The fix with MemoryRouter
Register MemoryRouter as an MCP server in Roo Code and the agent gets semantic recall plus a vault shared across your tools.
- 1
Add the server to the Roo MCP config
MCP settings (Roo Code)
{ "mcpServers": { "memoryrouter": { "type": "streamable-http", "url": "https://mcp.memoryrouter.ai/mcp" } } } - 2
Approve the server and sign in
Roo asks for confirmation before enabling a server. Complete the OAuth flow and pick the vault.
- 3
Migrate the useful parts of your bank
Move durable decisions into the vault and keep project facts in instructions. The bank can go back to being a small working file.
Connect Roo Code over MCP and share the vault with Claude Code and Codex. 14-day free trial.
Related
Roo Code memory FAQ
Sources
Sources checked 2026-09-25. Tool behavior changes; check the vendor docs before relying on a detail.