Amp memory: guidance files, thread by thread
Amp is a strong single-thread agent. The thread is where its context lives, and threads end.
Sourcegraph. Sources checked 2026-09-25.
How Amp handles memory today
Amp automatically includes AGENTS.md from the working directory, editor roots, and parent directories up to the home directory, plus subtree files when it reads inside them. That makes repository guidance portable across a team.
Amp also documents MCP support, including a registry allowlist, so external tool servers are a supported integration path where your organization permits them.
What Amp forgets
Files describe the repository. They cannot describe the week.
- Thread history when the thread ends, including the design discussion that produced the patch.
- Cross-project context, since AGENTS.md is scoped to the directories it sits in.
- Cross-tool continuity, unless something outside the tool holds it.
- The rejected approaches, which are usually the most expensive context to re-derive.
The fix with MemoryRouter
Where your Amp setup allows MCP servers, connect MemoryRouter and the agent can recall prior decisions and store new ones into your vault.
- 1
Check whether MCP is enabled for your account
Amp documents a registry allowlist, so confirm the server is permitted in your organization before wiring anything.
- 2
Register the remote server
MCP configuration
{ "mcpServers": { "memoryrouter": { "url": "https://mcp.memoryrouter.ai/mcp" } } } - 3
Keep AGENTS.md for instructions
Amp discovers guidance files up the tree, which is the right place for conventions. Memory holds the history those files should not carry.
Use it over MCP where Amp allows servers, and in your editor and CLI tools today. 14-day free trial.
Related
Amp memory FAQ
Sources
Sources checked 2026-09-25. Tool behavior changes; check the vendor docs before relying on a detail.