← Pando

Memory for Devin Desktop, now that Cascade’s is gone

Devin Desktop and Pando, for memory between sessions.

Windsurf’s Cascade wrote memories on its own and kept them on your machine, one set per workspace. Windsurf is Devin Desktop now, Cascade was removed in version 3.9.19 on 8 September 2026, and the docs are plain about the agent that replaced it: "The Devin Local agent does not persist memories between sessions."

Its Devin Local agent does not keep memories between sessions, so connect it to Pando and have it write the decisions into your outline, which every session and machine reaches, and so does every agent you allow to read it.

Set it up

  1. With the Devin CLI installed, run in a terminal: devin mcp add -s user pando https://pando.ink/mcp
  2. Run devin mcp login pando and approve the sign-in in Pando.

Devin Local asks before it calls any MCP tool until you allow the tool or the whole server, so the first session asks a few times. Without the CLI, put the same entry into mcp_config.json in your Devin config folder, and Devin asks you to sign in the first time it uses the server.

Where the old memories went

Nowhere by themselves. The docs point to a Cascade Migration Wizard that moves the ones you pick into skills, one item at a time. A skill is a procedure the agent runs when it fits. That suits "how we deploy" and suits "we chose Postgres in March, and here is why" much less well.

What each place is for

Working with other agents

The Devin CLI already reads your ~/.claude/CLAUDE.md as a global rule, so it borrows from Claude Code. With Pando the borrowing goes both ways: Claude Code, Codex and Cursor read and write the same outline, and what one of them decided is what Devin reads next.

What it costs

Nothing, for 1,000 bullets, with agents included and no card. Pando does not meter agent calls.

Deeper

Connect an agent, about two minutes · The twelve tools · Which note apps an agent can reach · Who runs this