Open Memory Protocol Initiative
Open Memory Protocol (OMP): an open protocol for moving and sharing AI-agent memory
About
The Open Memory Protocol Initiative (OMPI) is the multi-stakeholder, vendor-neutral open-source ecosystem with the goal of building an open protocol for agentic memory that allows memory to move between various agentic systems (interoperability) and for memory to be shared between systems. It is hosted at the AI Disclosures Project (housed at Code for Science & Society) and co-convened together with IBM and Mozilla. The GitHub repository is the technical and governance home of the ecosystem.
- Status
- pre-1.0
- Docs
- CC BY 4.0
- Code
- Apache 2.0
- Python
- 3.10+
- Discord
- Apply to join
Why an open memory protocol
The Open Memory Protocol (OMP) is an open protocol for moving and sharing AI-agent memory. Agent memory is persistent context that affects future model or agent behavior: user-provided facts, model- or agent-derived summaries, project instructions, prior decisions and actions, tool outputs, and references to underlying transcripts or artifacts.
Every major coding-agent harness (Claude Code, Codex, goose, OpenClaw, Letta Code) implements memory, but each uses a different convention: AGENTS.md, MEMORY.md, USER.md, HUMAN.md. Developers cannot move a stateful agent from one harness to another. Enterprises cannot switch memory providers without re-ingesting derived memory objects.
The fragmentation has real engineering and security costs. Provenance is often lost when memory is copied, and permissions that were meaningful in one system may not survive export. OMP is the smallest interoperable technology layer that addresses these costs, while allowing implementers to keep their own storage backends, ownership models, and internal architectures.
The first implementation focus is coding agents, where memory lock-in is most acute. Early implementations explore memory transfer across Claude Code, Codex, goose, and Letta Code.
December hackathon
We are holding an online mini hackathon in early December to align on the spec's goals and make progress on a draft implementation together. Vote on the date here!
Current stage
Working towards a version 1. No reference implementation exists yet. Current focus is on the exchange semantics and memory object. Next step is on the supporting shared memory components.
Join the OMPI Discord
Working-group discussion, implementer Q&A, and convening coordination. Membership is by application; tell us who you are and what you are building.
Apply for accessKey artifacts
Ecosystem roadmap
-
Dec 2026Online hackathon.
-
Q1 2027First spec and testing with implementation partners.
-
Q2–Q3 2027Launch with version 2.
-
Q3–Q4 2027More implementers; improving shared memory.
-
2028Governance and stewardship. Improved security and authorizations.


