AO2 Memory - Portable context for every AI. Never explain yourself twice.

You explain your project to one AI. Then you open another and explain it all over again — none of them share a memory. AO2 Memory is a shared memory layer. It's an MCP server you connect to whatever you use — Claude, ChatGPT, OpenClaw — so they all read and write to the same place. Tell one agent something, and the rest already know. And you stay in control: see what every agent did, roll back any change, and revoke access anytime.

Add a comment

Replies

Best
Hey PH 👋 I built AO2 Memory because I was losing my mind managing context across AI tools. I keep my notes and tasks in one place, but every AI tool lived in its own silo. I'd explain a project to Claude, then re-explain the whole thing to ChatGPT, then again to Claude Code. None of them knew what the others knew. I was the integration layer — copy-pasting my own context between tabs all day. So I built the thing I wanted: a shared memory layer my agents can all read and write to. It's an MCP server, so you connect it to whatever you use — Claude, ChatGPT, OpenClaw, your own apps via API — and they all draw from the same place. Tell one agent something, and the rest already know. Two things I cared about that most "AI memory" tools skip: • You actually own it, and it's structured. Not a mushy text blob that degrades over time — a real, structured store you define once, can export, and is yours. Think of your notes finally being legible to AI, instead of dumped into a black box. • You're in control. Every agent's changes are audited, you can roll back anything, and permissions are granular down to the field. The thing people fear about giving an agent access to their data — that it goes off and does something dumb — you can see it, undo it, and scope exactly what each tool can touch. Getting started is one prompt: tell Claude or ChatGPT "analyze what you know about me and load it into AO2," and your memory populates itself. From there it compounds — agents save what they pick up as you work, so the more you use it, the more it knows. I think of it as an audience of two (hence the name - ao2.ai) — just you and your AI. It's early and there's plenty I'm still building. Genuinely want the feedback. One question for you all: how are you managing context across your AI tools right now? Curious whether everyone's doing the same copy-paste dance I was, or if people have found something better.

 Congrats on the launch! 🎉 A shared memory layer across different AI tools sounds really useful. Does AO2 Memory work with locally hosted models as well, or only cloud-based agents?

 Thank you Nicole! It works with anything! If your local interface supports MCP, you can connect via MCP or if not, just use the API directly.

Congrats on the launch! 🚀

A shared memory layer across AI tools solves a problem I've run into many times.

I'm curious: if two agents update the same piece of memory with conflicting information, how does AO2 Memory resolve it? Does it support versioning, conflict detection, or require manual approval before merging changes?

 thank you Prashant! In this case the latest change will be the most up to date. But every record has a version history so the previous change will still be visible and you would be able to revert to it!

How do you prevent one agent from overwriting memory, like namespaces?

 so the latest updates take precedence but each record keeps a version history so you can roll back to any past version!