Cursor memory: rules, memories, and what each chat loses
Cursor gives you rules, past chats, and memory entries. None of them is a shared project brain, because each one lives inside Cursor and inside one workspace.
Anysphere. Sources checked 2026-09-25.
How Cursor handles memory today
Rules live in .cursor/rules as versioned files, and cursorrules-style plain files are read too. Memories are durable notes Cursor keeps for you, and @Past Chats lets a prompt reference earlier threads. Cursor also summarizes older conversation when the window fills, inside long-running sessions.
All of that is scoped to Cursor. Rules travel with the repository, but memories and chat context do not follow you into another tool, another editor, or another account.
What Cursor forgets
The failure mode is quiet. The chat looks fine, and the knowledge is simply not there.
- Chat context at the end of the conversation. A new chat in the same project starts from rules and memories only, which is why users keep a projectContext.md style file as a crutch.
- Summarized conversation. Auto-summarization rewrites older turns, so detail underneath the summary is gone while the summary reads fluently.
- Cross-tool continuity. What Cursor learned is not available to Claude Code, Codex, or ChatGPT.
- Team continuity. A teammate opening the same repository gets the rules files and not your memory entries.
The fix with MemoryRouter
Cursor supports remote MCP servers with OAuth. Point it at MemoryRouter and Cursor gains search_memories and store_memory tools that read and write a vault shared with every other connected tool.
- 1
Add the server to mcp.json
mcp.json
{ "mcpServers": { "memoryrouter": { "url": "https://mcp.memoryrouter.ai/mcp" } } } - 2
Enable it and sign in
Open Cursor Settings, then MCP. Cursor launches the OAuth flow in your browser so you sign in and pick a vault. No API key goes into a config file.
- 3
Ask for a recall on purpose
Memory over MCP is model-directed: Cursor decides when to call a tool. Prompt it directly ("check my memory for how we handle auth") to make the recall happen now.
The Cursor page has the full config, OAuth steps, and FAQ. 14-day free trial.
Related
Full Cursor guide
The Cursor page has the full config, OAuth steps, and FAQ. 14-day free trial.
Windsurf memory
Workspace memories plus a shared vault over MCP for Cascade sessions.
Claude Code memory
Keep project decisions across sessions and compaction with the published hook package.
Cursor forgets project context
Cursor is excellent inside a conversation and forgetful between them.
Cursor memory FAQ
Sources
Sources checked 2026-09-25. Tool behavior changes; check the vendor docs before relying on a detail.