Zed memory: instructions, threads, and the end of the thread

How Zed handles memory today

What Zed forgets

Instructions carry what to do. Threads carry what happened. Only one of them persists.

• Thread history when you move on. A new thread starts from instruction files, so the discussion that produced the code is not in the room.
• Cross-tool continuity. Zed instructions are read-only files, and nothing Zed learns flows to another assistant.
• Reasoning behind conventions. The .rules file states the standard; it does not carry the incident that set it.
• Anything decided in the middle of a long thread once it is compacted or abandoned.

The fix with MemoryRouter

Add MemoryRouter as a remote context server and Zed’s agent gains recall and store tools backed by your vault.

1. 1

   Add the context server to settings.json

   Zed settings.json

   {
     "context_servers": {
       "memoryrouter": {
         "url": "https://mcp.memoryrouter.ai/mcp"
       }
     }
   }

2. 2

   Authenticate

   Open Settings, then AI, then MCP Servers. Confirm memoryrouter shows a green status dot, and finish the OAuth sign-in Zed opens.

3. 3

   Name the server in the prompt

   Mentioning memoryrouter in a prompt makes the model more likely to call the right tool, the same way naming a file gets it read.

Related

Zed memory FAQ