GoodMemory v0.5.1: durable, auditable memory for coding agents

[hjqcan]

GoodMemory v0.5.1 is ready for people who want durable memory in Codex, Claude Code, or another MCP client without handing their project history to a hosted memory service.

GoodMemory sits between your agent host or application and the model runtime. It stores selected facts locally, recalls relevant context on later turns, and keeps writes auditable and reversible.

Try it with Codex or Claude Code

npm install -g goodmemory@0.5.1
goodmemory setup
goodmemory status

The interactive setup detects installed hosts and can use durable local SQLite without an embedding or extraction provider. Writeback is configurable: choose review if you want approval before durable writes, selective for governed high-signal writes, or off for recall-only use.

Other ways to use it

• Any MCP client: run goodmemory-mcp --standalone --user-id YOUR_USER_ID
• TypeScript applications: npm install goodmemory@0.5.1
• Python/FastAPI backends: use goodmemory-client with the HTTP bridge

Start here:

• Codex and Claude Code quickstart
• Standalone MCP setup guide
• v0.5.1 release notes
• Current status and evidence

If you try it, please share:

1. Which host and OS you used.
2. Whether goodmemory setup and goodmemory status worked on the first attempt.
3. One thing GoodMemory should remember better—or should never remember.

Bug reports belong in Issues. Setup experiences, integration questions, and host requests are welcome in Discussions.