memi v0.17 'Compound'. What shipped.
This post used to be called “v0.13 Tenacity”
The commit that published it renamed the file from v0-13-tenacity-release.md to v0-17-release.md, changed the codename to Compound, and jumped this site’s own package.json from 0.13.1 to 0.17.0, all in one diff (commit 52e408d, 2026-05-08). The release got renumbered mid-flight, four minor versions at once.
The reason is cadence, not vanity. The engine shipped v0.4.0, v0.5.0, and v0.6.0 within a single day in late March, and ran v0.4 through v0.7 inside roughly a week. The website’s version number was written down once and then left behind; by May the gap had grown to four minors. The draft post was describing a v0.13 that no longer existed anywhere except in the site’s own package.json.
So the renumbering was a correction toward reality. It still had a cost: an earlier version of this very post said “v0.13” in two places in the body, leftovers of the rename. When you change a number mid-flight, the old number keeps resurfacing in everything that was drafted against it. Worth it, but not free.
What Compound actually is
One project-memory store, with every surface reading and writing it. Update a spec from any surface and every other surface sees it. No re-explaining the architecture on session one hundred, no re-extracting the same design system per tool.
The engine side of the release landed the day before in one feature commit: Studio simulation, swarm v2, automations, the Codex plugin, vibe design, and agent-kits (commit 079b8e15, 2026-05-07), with 19 new agent and motion Notes alongside. The 0.17.0 cut itself, version pinning across tests and the Studio runtime, and final polish for scroll behavior and harness chips all landed the same day (commit 2cecd224, 2026-05-07).
Per surface:
CLI (@memi-design/cli). memi diagnose, memi pull, memi spec, memi generate, and memi compose all hydrate from the shared memory store. The --from <directory> flag works on any project, not just the active workspace.
Studio (macOS app). The agent-runs cockpit, Figma cockpit, and trace browser surface the same memory through a native UI. Switching workspaces does not lose context.
Harness. Routing across Claude, Codex, Hermes, Ollama, OpenCode, and local tools, with sandboxed tool execution and a full replayable trace per run.
MCP server. memi mcp start exposes 14 tools and 3 resources to any MCP-compatible client (Claude Code, Cursor, Windsurf). Spec creation, code generation, design-system pulls, and Figma operations are callable as tools.
Codex plugin. memi agent install codex-plugin gives the model the same memory surface the CLI uses.
The mechanism holding this together is bidirectional sync hashing over a typed workspace store. The deep dive that shipped alongside this post walks the whole thing: the directory map, every command, the routing matrix, the agent loop, and the .memoire workspace tree (same commit 52e408d).
Update, May 9: the version lied for a day
One day after this post, the Studio app split into its own repo and immediately produced the best version-numbering lesson of the release.
Studio pinned its runtime at 0.18. The actual published tarball was named memoire-runtime-resources-0.17.0.tar.gz, because the engine’s 0.18.0 version bump existed only in an uncommitted working tree at publish time. The pin said one thing, the artifact said another, and a same-day correction had to reconcile them (commit 1e36149, 2026-05-09).
I am leaving that in the release post because it is the honest postscript to the renumbering story above. A version number is real when it exists in a committed tag and on a published artifact, and nowhere short of that. Release notes are claims. Tarballs are facts. This release had its notes corrected toward the artifacts twice in 48 hours, once on the website and once in the runtime pin, and both corrections are in the log.
Why “Compound”
Because the value model changed from per-run to cumulative. Before this release, every agent session started from zero and the discovery tax got paid every time. With one store under the CLI, Studio, the MCP, and the Codex plugin, work done in any surface raises the floor for all of them. The codename is the thesis.
Source is on GitHub. Notes pack at github.com/sarveshsea/memoire-notes. Ship issues, PRs, or feature requests. There is no business behind this. Nobody is making money. Just a tool.