Why this exists
A memory you cannot read, correct, or take with you is not really yours. So everything Mengram stores comes back out as plain Markdown: one file per thing it remembers, relations as[[wikilinks]], procedures with the record of them
working and the log of why they changed.
The export is deliberately not charged against your add or search quota.
Getting your data out should never cost you the ability to use the product.
The per-minute rate limit still applies.
From the CLI
Without
--force the command refuses to overwrite an existing memory/
folder, so a second run cannot quietly replace something you edited.
From the API
string
default:"markdown"
markdown returns a zip of the tree. files returns the same tree as
{path: text} for clients that write files themselves. json returns the
underlying records.string
default:"default"
Which sub-user’s memory to export.
What you get
git diff shows what your agent learned this week, a pull request
reviews something it learned wrongly, and git revert undoes it.
Into an Obsidian vault
The Obsidian plugin does this without the terminal: run Pull memory into vault from the command palette. The folder it writes is generated — anything you edit inside is replaced on the next pull, so keep your own notes elsewhere.The format is published separately
The tree above is memfmt, a small open format with its own library and specification. Mengram writes it; the library reads it without an account or a server. That separation is the point: if you stop using Mengram, the files keep working.Reading a folder back into Mengram is not built yet. Export is one-way today.