Exporting what your agent remembered
Every assistant now lets you read what it remembers about you. None of the big three lets you take it with you. Claude shipped memory import in March 2026 and no export; Gemini’s personal context is not available in the EEA at all.
From Pando, yes: the memory is a branch of your outline, and it exports to Markdown, OPML, a spreadsheet or a whole-account backup at any time, without asking anybody.
Set it up
- Point the client at https://pando.ink/mcp, which speaks streamable HTTP.
- Authenticate with OAuth 2.1 and dynamic client registration, or paste a key from Agents and API keys as a Bearer token.
The test the market named, and our reading on it
The yardstick published on 27 July 2026 is a round trip: export it, import it into a clean instance, export again, and diff. The essay’s conclusion was that most systems fail, because a cache treated as a system of record is how you end up unable to leave.
Every run of our test suite does exactly that, through the public doors, between two accounts that share nothing. On 22 September 2026 the reading was 1,267 bytes of OPML and 567 bytes of Markdown, out of two accounts, identical. Not equivalent. The same bytes.
What that does and does not prove
It proves the file we write is the file we read, and that nothing is lost or reshaped between two accounts. It does not prove that an OPML file opens correctly in somebody else’s importer, because their importer is theirs. What can be said is narrower and still useful: it is plain text, and plain text outlives software.
Why this matters more than it sounds
An agent memory you cannot export is a memory that belongs to a vendor. The longer it runs, the more it is worth, and the more the cost of leaving rises. A memory that comes out whole has the opposite shape: it gets more valuable to you rather than more expensive to leave.
Deeper
Connect an agent, about two minutes · The twelve tools · Which note apps an agent can reach · Who runs this