Overview Research Convenings Prototypes Writings Talks People
Newsletter

A multi-stakeholder ecosystem for portable AI memory

OMPI incubates open, interoperable specifications for portable AI memory. It is housed at the AI Disclosures Project, a project of Code for Science & Society, and runs as a light-weight working group with in-person convenings and monthly digital meetings.

The goal is decentralized, competitive AI markets with specialized producers and modular technological pieces.

Specifications are model-, harness-, and application-agnostic. Multi-user memory, provenance, and privacy are first-order design considerations. In AI systems, memory is part of the context layer that enables personalization and agentic action — user-provided or model-learned, scoped to a project, user, or organization.

Artifacts and specs

OMP v0.1 spec

Draft OMP technology by Charles Packer (Letta).

Read draft

OMP v0.2 spec

Expanded schema, provenance, and lifecycle. Charles Packer (Letta).

Read draft

me.md

User-owned plain files. Agents propose; users decide. David Hamilton (Block / goose).

View on GitHub

AMS Card

Structured documentation format for memory systems. By Mila and Mozilla.

View on GitHub

State of agent memory

Survey of memory implementations across coding, consumer, and enterprise systems (Aug 2026).

Read note

Reference Python code

Loader, validator, and harness contract. Apache 2.0.

View on GitHub

Governance model

Technical Steering Group, consensus decisions, royalty-free licensing, Month-24 review.

Read governance

Memory is becoming a core agent layer without shared exchange semantics

Agent memory is persistent context that shapes future model or agent behavior — user facts, derived summaries, project instructions, prior decisions and actions.

Every major coding-agent harness (Claude Code, Codex, goose, OpenClaw, Letta Code) implements memory with a different convention. Developers cannot move a stateful agent across harnesses. Enterprises cannot switch memory providers without re-ingesting derived objects. Open-source memory projects duplicate one another for lack of a shared object model.

Fragmentation has engineering and security costs: bespoke adapters, lost provenance on copy, permissions that don't survive export, harder security review. A common open layer addresses this without dictating how each agent reasons, summarizes, indexes, or retrieves.

Partners and implementers

Partner

Mozilla

Co-hosts convenings, leads ecosystem recruitment across Mozilla's open-source and AI-developer network.

Raffi Krikorian (CTO) · Matt Harris
Partner

IBM

Co-hosts convenings, contributes enterprise-adoption pathways, advises on standards-body process.

Gabe Goodhart (Chief Architect) · Anna Lisa Gentile · Rynne Whitnah
Specification collaborator

Letta

Contributes MemGPT / Letta memory-object model and the open-source Trajectory package.

Charles Packer (Co-founder and CEO)
Implementation collaborator

Block / goose

Open-source agent harness on the Model Context Protocol. First-vertical implementation target.

goose maintainer team

From ecosystem launch to sustainable stewardship

Sept 9, 2026
First ecosystem convening (online). Co-hosted with Mozilla and IBM.
Oct 2026
In-person gathering at the O'Reilly open-source unconference (Berkeley). Reference Python implementation (v0.1) published.
Year 1 (2026–27)
Two coding-agent harnesses shipping conformant memory export/import. First cloud-provider integration.
Year 2 (2027–28)
OMP v1.0 released. Six harnesses conformant. Preliminary IETF engagement.
End of award
Long-term stewardship in place. Continued AI Disclosures Project / CS&S stewardship as default; Agentic AI Foundation affiliation as a candidate transition path.

Join the ecosystem

If you build agent memory, maintain a coding-agent harness, run a memory-layer service, or contribute to open AI infrastructure, join OMP.

Email OMPI GitHub