MemorySafe 0.4.2
MemorySafe 0.4.2
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 and open it with
Claude Desktop. Restart the assistant either way, then open
http://127.0.0.1:8765/dashboard to confirm.
One install route per host, and a way to tell it worked. Each assistant has one
route and one confirmation. Claude Desktop has no claude command, so its section
says so rather than leaving you to find out. The restart, and the one-off wait
while the runtime builds, come before the commands instead of after.
memorysafe migrate has a Windows path. It listed only macOS and Linux, in the
release that announced Windows parity.
The dashboard stopped calling your computer a Mac. It is served on every platform.
memorysafe doctor reports more, and no longer crashes. It says when the
prompt-time capture hint cannot run on Windows, shows %LOCALAPPDATA%\MemorySafe
instead of the long redirected path Claude Desktop's packaged build produces, and
names a dashboard left behind by an older install that is still holding the
address. A status it did not recognise used to make the command fail with an
error instead of printing the report.
The published documents come from one source, so the two public READMEs cannot
drift apart again, and a test fails if they ever describe different install
routes or migrate paths.
The privacy policy ships beside the licence that incorporates it. The Beta Terms
name it as forming part of the Terms in four places, and it was published nowhere.
ChatGPT on the web is no longer documented as an install route. Reaching it needs
a separate tunnel and developer mode, and it cannot be listed the way the plugin
is. Existing tunnel installs are untouched and keep working.
Upgrading from 0.4.1 does not rebuild your runtime: requirements.lock and the
Python pin are unchanged.