Windsurf memory: workspace-scoped, and easy to leave behind
Cascade memories are genuinely useful and genuinely local. They live per workspace on one machine, which means a new conversation, a new checkout, or a new laptop all start at zero.
Windsurf (Cascade). Sources checked 2026-09-25.
How Windsurf handles memory today
Windsurf documents two mechanisms. Memories are auto-generated notes stored locally per workspace, retrieved when relevant, and never committed or shared. Rules are user-defined instruction files that shape behavior.
Cascade also supports MCP, and the same docs note a memory MCP server as an option. That is the seam where a durable, cross-tool vault fits.
What Windsurf forgets
Local and workspace-scoped means useful today and gone tomorrow.
- Everything on a new machine. Memories live under the local Windsurf directory, so a second laptop has none of them.
- Everything for a teammate. Nothing is committed, so sharing a repository does not share the memory.
- Cross-workspace context. A memory from one workspace does not arrive in another, even when the projects are two halves of one system.
- Context at the end of a conversation. The next conversation starts from memories and rules, not from what you just discussed.
The fix with MemoryRouter
Add MemoryRouter as a remote MCP server and Cascade gains recall and store tools backed by a vault that also serves your other tools.
- 1
Add the server to mcp_config.json
mcp_config.json
{ "mcpServers": { "memoryrouter": { "serverUrl": "https://mcp.memoryrouter.ai/mcp" } } } - 2
Authenticate
Open the MCP panel, find memoryrouter, and finish the OAuth sign-in. Pick the vault you want Cascade to use.
- 3
Name the project on writes
Because the vault is shared, ask Cascade to save under a project name so recall stays precise when several projects are in flight.
Full config and verification steps on the Windsurf page. 14-day free trial.
Related
Full Windsurf guide
Full config and verification steps on the Windsurf page. 14-day free trial.
Cursor memory
Connect the vault as a remote MCP server so new chats open with project decisions.
Cline memory
Memory Bank discipline plus a shared vault over MCP for cross-session recall.
Zed memory
Agent panel threads plus a shared vault over a remote context server.
Windsurf memory FAQ
Sources
Sources checked 2026-09-25. Tool behavior changes; check the vendor docs before relying on a detail.