Kilo Code memory: Memory Bank is out, AGENTS.md is in
Kilo Code made a clear call: project memory is a file in the repository. That is simpler and more honest than a bank of self-maintained notes, and it moves the history problem to you.
Kilo Code. Sources checked 2026-09-25.
How Kilo Code handles memory today
Kilo Code deprecated the Memory Bank in favor of AGENTS.md. Existing Memory Bank rules still function, but status indicators like active or missing are no longer guaranteed across clients and modes, and the docs point at AGENTS.md for migration.
Kilo Code supports MCP servers, so a remote memory service connects natively alongside the instruction file.
What Kilo Code forgets
One file can hold instructions. It cannot hold a running record of everything you decided.
- Session history between tasks, unless a person writes it down.
- The reasoning inside a long session that never reached the file.
- Cross-tool continuity, because AGENTS.md is read by agents but not written by them as a history.
- Anything from a different project, since the file lives in one repository.
The fix with MemoryRouter
Connect MemoryRouter over MCP and Kilo Code gets a memory layer that survives task boundaries and shares with your other tools.
- 1
Add the server to Kilo Code MCP settings
MCP settings
{ "mcpServers": { "memoryrouter": { "url": "https://mcp.memoryrouter.ai/mcp" } } } - 2
Authenticate and pick a vault
Approve the server, then complete the OAuth flow in the browser tab Kilo Code opens.
- 3
Keep AGENTS.md for instructions
Build commands, structure, and conventions stay in the file. Decisions and session context go to memory, which keeps the file from becoming a changelog.
Connect Kilo Code over MCP and share the vault with every other tool you use. 14-day free trial.
Related
Kilo Code memory FAQ
Sources
Sources checked 2026-09-25. Tool behavior changes; check the vendor docs before relying on a detail.