--- title: "Mémoire v0.17 'Compound'. What shipped." description: "Mémoire CLI, Studio, the harness, the MCP, the Codex plugin. v0.17 is the release where every surface pulls on the same memory." publishDate: 2026-05-08T00:00:00.000Z author: Sarvesh Chidambaram tags: ["release", "studio", "mcp", "codex"] canonical: https://memoire.cv/blog/v0-17-release --- ## TL;DR The npm package, the macOS Studio app, the MCP server, and the Codex plugin now share a single project-memory store. Update a spec in one surface, every other surface sees it. No re-discovery, no re-extraction, no re-paying the discovery tax on every run. ## The problem If you have ever wired Claude into a real codebase, you know the shape of the problem. The first session is exciting. The second session is fine. The hundredth session is depressing. You have re-explained the same architecture, the same conventions, the same constraints a hundred times. Reasoning is not the bottleneck. Memory is. Most agent harnesses solve this with a project README. That works until the project grows past one file. Mémoire v0.13 ships the same idea but with structure: a typed memory store that every surface (CLI, Studio, MCP, Codex plugin) reads from and writes to. ## What shipped **CLI** (`@sarveshsea/memoire`). `memi diagnose`, `memi pull`, `memi spec`, `memi generate`, `memi compose` all hydrate from the new memory store. The `--from ` flag works on any project, not just the active workspace. **Studio** (macOS Tauri app). The agent-runs cockpit, Figma cockpit, and trace browser all surface the same memory through a native UI. Workspaces can be switched without losing context. **Harness** (Hermes + Mirofish). 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 now all callable as MCP tools. **Codex plugin**. The same harness, exposed inside Codex. Run `memi agent install codex-plugin` and the model gets the same memory surface the CLI uses. ## What's next v0.14 will focus on multi-agent: long-running agents that share memory across sessions and hand off to each other. The infrastructure landed in v0.13. The interaction model is what's next. Source on [GitHub](https://github.com/sarveshsea/m-moire). Notes pack on [github.com/sarveshsea/memoire-notes](https://github.com/sarveshsea/memoire-notes). Ship issues, PRs, or feature requests. There is no business behind this. Nobody is making money. Just a tool.