Continue memory: rules for behavior, nothing for history
Continue gives teams a configurable assistant inside the editor. Configuration is portable; conversation is not.
Continue. Sources checked 2026-09-25.
How Continue handles memory today
Continue documents rules that agents follow: markdown or YAML files for coding standards, security practice, and verification steps, with glob and regex filters so a rule applies to the right files.
Rules shape behavior. They do not store what happened, so an agent session that solved a subtle problem leaves nothing behind except the diff.
What Continue forgets
Rules are the setup. History is the work, and it is not saved.
- The session itself. Close it and the reasoning is gone, while the rules file stays exactly as you wrote it a month ago.
- Accumulated decisions. There is no place in the config where "we chose this over that" naturally lives.
- Cross-session context in a team. Two engineers using the same config still start with separate, empty histories.
- Cross-tool continuity with whatever else your team runs.
The fix with MemoryRouter
Continue supports remote MCP servers, and MCP servers run in agent mode. Add MemoryRouter and the agent gets a durable memory it shares with your other tools.
- 1
Add the server to config.yaml
config.yaml
mcpServers: - name: MemoryRouter type: streamable-http url: https://mcp.memoryrouter.ai/mcp - 2
Switch to agent mode and authenticate
MCP servers only run in agent mode. Open the MCP servers list and complete the OAuth sign-in for memoryrouter.
- 3
Test recall across sessions
Save a unique fact in one session, start a new one, and ask Continue to check its memory. That is the moment the difference is obvious.
Continue also auto-loads JSON MCP config files dropped in .continue/mcpServers/, which makes team rollout a single file in the repository.
Config block and verification steps on the Continue page. 14-day free trial.
Related
Full Continue guide
Config block and verification steps on the Continue page. 14-day free trial.
Zed memory
Agent panel threads plus a shared vault over a remote context server.
Cursor memory
Connect the vault as a remote MCP server so new chats open with project decisions.
Claude Code memory
Keep project decisions across sessions and compaction with the published hook package.
Continue memory FAQ
Sources
Sources checked 2026-09-25. Tool behavior changes; check the vendor docs before relying on a detail.