PMB
Local-first persistent memory for Claude Code, Cursor, Codex, and Zed via MCP.
PMB solves a genuine pain point for AI-assisted coding: context loss between sessions. Its local-first, MCP-native design is fast and private, with recall under 100ms and zero cloud dependency. But setup requires CLI comfort and MCP configuration — it's not a plug-and-play product.
- Developers using AI coding agents who want persistent context
- Teams working with multiple agents who need shared memory
- Users who prioritize data privacy and offline-first tools
- Developers tired of re-explaining project context each session
- Users who need cloud sync or team sharing natively
- Non-technical users unfamiliar with CLI or MCP setup
- Those seeking a turnkey product with no local configuration
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
In short
PMB — Local-first persistent memory for Claude Code, Cursor, Codex, and Zed via MCP. Best for Developers using AI coding agents who want persistent context, Teams working with multiple agents who need shared memory, Users who prioritize data privacy and offline-first tools. Free to use.
Viability Score
How likely is PMB to still be operational in 12 months? Based on 4 signals — momentum (how recently it shipped), wrapper dependency, revenue model, and web presence.
Last calculated: July 2026
How we score →Key Features
- Persistent SQLite memory file on disk
- MCP-native integration with Claude Code, Cursor, Codex, Zed
- Sub-millisecond classification and recall (~35 ms)
- Auto-inject relevant lessons, decisions, and project overview on every prompt
- Hybrid recall (BM25 + dense vectors + entity graph + optional rerank, fused with Reciprocal-Rank-Fusion)
- Honest impact scoring: tracks whether each lesson is followed, flags dead memories
- Local web dashboard with interactive entity graph (Map) and git-style timeline
- Async writes: SQLite first, embedding and vector insert on background thread
- Works offline, no API keys, no telemetry
- Open source under Apache 2.0 license
- Inspectable and exportable memory chunks
- Entity nodes color-coded by type, sized by importance
- Multi-project support with navigation lanes
About PMB
PMB gives your AI coding agent a permanent memory that lives entirely on your disk. It stores decisions, lessons, goals, project facts, and recent work in a single SQLite file, fed back to the agent through the Model Context Protocol (MCP). No cloud services, no API keys, and no LLM call on the read path — recall happens in ~35 ms. Designed for developers using Claude Code, Cursor, Codex, or Zed, PMB stops the repetitive cycle of re-explaining your project every session. The agent automatically receives relevant context before reasoning, and journals its work afterward. An open-source dashboard provides a visual map and timeline of all memories, with entity graphs and git-style journaling. Honest impact tracking scores each lesson by whether the agent actually follows it, flagging dead memories so you can prune what doesn't help. The tool is offline-first, inspectable, and exportable, giving you full control over your project's context.
Behind the Verdict
PMB addresses a real and annoying problem for anyone using AI coding agents: every new session starts from zero. By giving agents persistent, locally-stored memory via MCP, PMB eliminates the repetitive re-explaining of project context. Its hybrid recall (BM25 + dense vectors + entity graph) is both fast and accurate, clocking in at ~35ms for most queries. The honest impact scoring — which tracks whether lessons are actually followed — is a thoughtful feature that keeps memory lean and relevant. Where PMB shines is in multi-agent workflows: Claude Code, Cursor, Codex, and Zed all read the same SQLite file, so context follows your project, not your editor. It's also refreshingly private: no cloud, no telemetry, no API keys. All data stays in a single SQLite file and a LanceDB vector store on your disk. The trade-off is that PMB is decidedly developer-focused. Setup requires pip install and running pmb connect commands in the terminal. Non-technical users will struggle. There's no native cloud sync or team sharing, which limits collaboration out of the box. Compared to alternatives like MemoryGPT (which is cloud-hosted) or Copilot's session memory, PMB wins on privacy and speed but loses on ease of use. We'd recommend it for solo developers or small teams already comfortable with CLI tools and MCP; for anyone expecting a polished turnkey product, it's not there yet.
Researching PMB? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Use Cases
- Persist project conventions and decisions so Claude Code remembers them across sessions.
- Share context between Cursor and Codex without manual copying.
- Track which coding rules your agent actually follows and prune ineffective ones.
- Visualize your project's memory as an entity graph to spot knowledge gaps.
- Review a git-style timeline of decisions and lessons learned over the project lifecycle.
Limitations
- No multi-user collaboration or cloud sync out of the box.
- Requires manual MCP setup with each agent.
- Memory recall depends on local file quality—no automatic deduplication or conflict resolution for overlapping lessons.
Integrations
Resources & Guides
Official links
Tools that pair well with PMB
Common stack mates teams adopt alongside PMB, with the specific reason each pairing earns its keep.
Featured Head-to-Head Comparisons
Alternatives to PMB
View allPieces for Developers
OS-level automatic memory for developers that captures code, docs, and chats without interrupting flow
Frequently Asked Questions
Best-of guides
Used PMB? Help shape our editorial sentiment research.