PAXM
Provider-neutral memory adapter for coding agents, with local SQLite and MCP.
PAXM is an open-source memory adapter that carries decisions, conventions, and working context across Codex, Claude Code, OpenCode, Pi, and MCP clients. It starts with local SQLite and can route recall and writes to multiple supported memory providers.
Official resources
Selection advice
Quick comparison
PAXM keeps one agent-facing memory contract while letting operators choose local SQLite or supported remote providers. Mem0 is designed for memory embedded in applications, while EverOS uses Markdown as its source of truth.
| PAXM | Mem0 | EverOS | |
|---|---|---|---|
| Best for | Sharing coding-project context across multiple agent clients | Embedding user memory in an agent application | User-owned, Markdown-native memory across local tools |
| Storage model | Built-in SQLite or routed writes and recall across supported providers | SDK-managed memory with self-hosted and managed options | Markdown source of truth with SQLite and LanceDB indexes |
| Integration style | CLI, MCP tools, skills, plugins, and lifecycle hooks | Python and TypeScript APIs inside application code | Local runtime, REST API, MCP, and coding-assistant integrations |
| Tradeoff | Early v0.1.x project focused on agent clients rather than a hosted memory UI | Application-friendly SDK with more provider setup than local SQLite | Inspectable files with a heavier local runtime and indexing stack |
Best for
- cross-agent coding context
- local-first memory
- provider-neutral routing
- passive session recall and capture
Not ideal for
- teams seeking a fully managed memory service and hosted UI
- products that need an in-application memory SDK for end users
- environments that cannot run a local CLI, MCP server, or agent hooks
Core concepts
Minimal implementation shape
Install the CLI, run `paxm setup`, save a decision with `paxm remember --profile ltm --text "Use SQLite locally"`, then retrieve it in a later session with `paxm recall --query "local storage"`.