MemoryRouter
Fix

Cursor forgets project context between chats

Cursor is excellent inside a conversation and forgetful between them. Start a new chat in the same repository and the rules file is basically all that carried over.

Sources checked 2026-09-25.

Why Cursor resets

Chat context is scoped to the chat. Rules live in .cursor/rules as files and are the durable layer, which is why teams keep a project context document and @-mention it constantly.

Long sessions degrade differently: older turns get summarized as the window fills, so details drop while the summary reads fluently. In public bug reports users describe the same exchange count before the session starts recapping as if it had just begun.

Cursor memories and past chats help, and they are still inside Cursor, on one workspace, for one account.

Free fixes you can do today

These work today, with no new tools.

  1. 1

    Keep a short decisions file and @-mention it

    The long-standing community workaround is a top-level project context document that summarizes the project and current tasks. Reference it at the top of a new chat.

  2. 2

    Write rules for standards, not history

    Rules work best for conventions and commands. Stuffing history into rules makes them long, expensive, and rarely read.

  3. 3

    Use @Past Chats deliberately

    Cursor can reference earlier threads. Naming the right one is faster than re-explaining, when you remember which thread had the answer.

  4. 4

    One chat per task

    Shorter chats summarize less. Fewer silent rewrites of your earlier turns.

The durable fix

Cursor supports remote MCP servers with OAuth. Connect MemoryRouter and Cursor gains search and store tools for a vault shared with your other tools, so project memory is not trapped in one workspace.

Recall over MCP is model-directed: Cursor calls the tools when the prompt warrants it, and you can ask for a recall explicitly when it matters.

  1. 1

    Add the server to mcp.json

    mcp.json

    {
  "mcpServers": {
    "memoryrouter": {
      "url": "https://mcp.memoryrouter.ai/mcp"
    }
  }
}
  2. 2

    Enable it and sign in

    Open Cursor Settings, then MCP, and complete the OAuth flow. Pick the vault Cursor should use.

  3. 3

    Ask for a recall

    Prompt "check my memory for how we handle auth" and watch it return last week’s decision instead of guessing.

Full setup guide: Cursor setup guide

Connect Cursor to MemoryRouter

Config, auth, and FAQ on the Cursor page. 14-day free trial.

Related

Cursor memory

Connect the vault as a remote MCP server so new chats open with project decisions.

Windsurf memory

Workspace memories plus a shared vault over MCP for Cascade sessions.

re-explain codebase every session

Ten minutes of orientation, every session, forever.

FAQ

Sources

Sources checked 2026-09-25. Tool behavior changes; check the vendor docs before relying on a detail.

Start free