Cody memory: repository context per chat, and the enterprise flag

How Cody handles memory today

What Sourcegraph Cody forgets

Repository context is not project memory, and a chat boundary erases the difference.

• Conversation history at the end of the chat, including the constraints you explained along the way.
• Any memory outside the repository. Decisions live in people and in tools like Claude Code, not in code comments.
• Cross-tool continuity, and in the default setup, cross-chat continuity too.
• External context on non-enterprise plans, where MCP tooling is not available at all.

The fix with MemoryRouter

Where Cody can call MCP tools, bridge it to MemoryRouter with mcp-remote and the vault becomes another source of grounded context.

1. 1

   Confirm the enterprise requirement

   MCP support in Cody runs through agentic context fetching, which needs a Sourcegraph Enterprise instance with the agentic-context-mcp-enabled flag on. Verify first; there is no user-level switch for this.

2. 2

   Add the bridge to VS Code settings

   settings.json (JetBrains uses cody_settings.json)

   {
     "cody.mcpServers": {
       "memoryrouter": {
         "command": "npx",
         "args": ["-y", "mcp-remote", "https://mcp.memoryrouter.ai/mcp"]
       }
     }
   }

3. 3

   Verify with a recall

   Ask Cody to search memory for a fact you stored from another tool, which also confirms the OAuth bridge is signed in.

Related

Sourcegraph Cody memory FAQ