paxm
Persistent, provider-neutral memory for Codex, Claude Code, OpenCode, Pi, and MCP coding agents.
What is it?
What it is
PAXM carries decisions, conventions, and working context into later Codex, Claude Code, OpenCode, Pi, Cursor, TRAE, Kimi Code, ZCode, Kiro, Cline, and MCP
Why it exists
Persistent, provider-neutral memory for Codex, Claude Code, OpenCode, Pi, and MCP coding agents.
Who should use it
Teams building with Go who want an open-source, self-hosted option.
Who should avoid it
Teams that need a fully managed SaaS with enterprise SLAs out of the box.
How it works
A quick walkthrough in plain English
How paxm works
Step 1 of 3
You interact with it
Open paxm, send a request, or connect it to your stack.
Features
Advantages
- Open source (Apache-2.0)
- Active Go ecosystem
- Self-hosted deployment options
Disadvantages
- Requires operational ownership for self-hosted setups
- Community support varies by project maturity
Installation
native
paxm remember --profile ltm --text \ "Production deploys run through GitHub Actions; never deploy from a laptop"
FAQ
What is paxm?
paxm is an open-source project licensed under Apache-2.0.
What language is paxm built with?
Primary language: Go.
Is it free to use?
Yes. Licensed under Apache-2.0. Check the license for commercial use.
Featured in Videos
YouTube tutorials and walkthroughs for paxm
Alternatives
Similar projects ranked by category, topics, and text overlap.
