MemorySafe 0.4.7
MemorySafe 0.4.7
Install or update
Claude Code and Codex update themselves from the marketplace. New installs:
claude plugin marketplace add MemorySafe-Labs/memorysafe-plugin
claude plugin install memorysafe@memorysafe
codex plugin marketplace add MemorySafe-Labs/memorysafe-plugin
codex plugin add memorysafe@memorysafe
Claude Desktop has no claude command: download the .mcpb below, then in Claude
Desktop choose it from Settings -> Extensions -> Advanced settings -> Install Extension....
Don't double-click it: on some computers Windows opens it in Notepad. Restart the
assistant either way, then open http://127.0.0.1:8765/dashboard to confirm.
What changed
You can take MemorySafe off this computer with one command. memorysafe uninstall lists
everything it put here, with sizes, and changes nothing until you add --apply. Plugins leave
through each assistant's own installer, and the private runtime, the local state and any
hand-written registration go with them. Your memories stay unless you add --purge, which
copies the database to your home folder first and tells you where. Claude Desktop asks you to
confirm what its extensions do, so removing that one stays with you, and the command says so.
Other MCP clients can share the same memory. Cursor, VS Code, Windsurf and anything else
that speaks MCP can use bin/memorysafe-mcp in your MemorySafe folder as the command to run.
It is rewritten on every start, so it keeps working across updates.
The dashboard opens itself, once. On the first start after an install it shows itself
rather than leaving you to type an address. Once only, never again, and
MEMORYSAFE_OPEN_DASHBOARD=0 turns it off.
The Claude Code row says what connecting it is for. If you have the Claude Desktop
extension, sessions inside the desktop app already reach MemorySafe through it. The dashboard
now says so, and that connecting Claude Code is for using it in a terminal, where the
extension cannot reach.
The Beta Terms of Use and Privacy Policy now describe this product. They were written for
a ChatGPT-only beta and said that every request passed through OpenAI's systems. That was
never true of Claude Code, Claude Desktop or Codex, which reach MemorySafe on your own
computer, and Anthropic was named nowhere. The documents now say where your memories actually
go. They are version 0.2, so the dashboard will ask you to read and accept them again --
nothing stops working while you do, and your memories are untouched.
Fixed
On Windows, editing the launcher could silently stop the memorysafe command from being
created. cmd.exe finds a label in a batch file by byte offset, and on a file with Unix
line endings it can miss. One added line was enough, and nothing reported it: the server
still started, so only the first-run test noticed the command was never written.
migrate missed MemorySafe registrations inside individual projects, so a project could
still load it twice. It now finds them in ~/.claude.json and in project .mcp.json files,
and removes them only when that assistant's plugin is installed.