MemorySafe 0.4.9

MemorySafe 0.4.9

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

MemorySafe's old registration in Codex could stop Codex loading any tools at all.
Installs going back to 0.3.x wrote a [mcp_servers.memorysafe] block into
~/.codex/config.toml using Windows paths that TOML cannot read. The whole file then
failed to parse, so Codex started with none of its MCP servers -- not only without
MemorySafe. Nothing writes that block any more, and memorysafe migrate removes an old
one. If Codex has been quietly missing its tools, this is worth checking.

If that entry keeps coming back, close Codex before you remove it. Codex writes
config.toml from what it holds in memory, so an entry deleted while it is running
reappears the next time it saves. That is not MemorySafe rewriting itself, and
memorysafe migrate now says so before you run it.

Everything in 0.4.7 and 0.4.8 is included: the uninstaller, the launcher for other MCP
clients, the dashboard opening itself once, the corrected Beta Terms of Use and Privacy
Policy, and the fix for doctor and uninstall stopping with an error instead of
printing their report.

For anyone working on MemorySafe

A first-start window thread could outlive the test that started it and open a browser
during an unrelated test, which showed up as a rare CI failure on Linux. The launcher
now exposes that thread as its own seam and the tests stop it for a whole module.