Saving is easy. Managing is everything.
Merso is open-source long-term memory for AI agents. One memory for every project and every tool you work in, kept in your own cloud and reconciled every day, so your agents know what is true now, not just what was once said. Use it for your own work, or build it into the AI apps you ship.
In design. Built in public and used daily before the first release.
- Memorize
- Extract
- Reconcile
- Surface
- Own
Most memory systems stop at M and E. Merso is built around R.
A pile of notes is not a memory
Every session starts from zero.
Your agent relearns the project, your preferences and last week’s decisions each time you open it.
Recording everything is not remembering.
Tools that save every step keep the old fact next to the new one. Your agent can’t tell which is true.
Memory is split by tool and by repo.
Work done in Codex never reaches Claude Code. A decision made in one project never reaches the next.
You can’t see what your agent knows.
Memory hidden in a database can’t be read, questioned or corrected.
What reconcile means
Each day Merso compares what happened with what it already knows. Changed facts get an end date instead of being overwritten, names that mean the same thing merge, and one-off details expire.
New from today
Codex session in atlas-web, Oct 14
- Moved the database from Postgres to Cloudflare D1.
- Fixed the login redirect in the dashboard app.
- Port 4321 was busy, so I used 4322.
Memory
- factAtlas runs on Postgressince Sep 2Sep 2 to Oct 14
- factAtlas runs on Cloudflare D1since Oct 14
- thingAtlasalso atlas-web, “the dashboard app”since Aug 30
- thingatlas-websince Sep 12
- factLogin redirect fixed in AtlasOct 14
- noteUsed port 4322, 4321 was busyexpires Nov 13 unless linked
3 new items to reconcile.
How it works
Five steps for every session and every day. The first two are easy. The third is the reason Merso exists.
Memorize
An adapter in Claude Code, Codex, Flue or your own agent sends each finished session to your Merso. Nothing to do by hand.
Runs in your tools
Extract
A model reads the session and pulls out what matters: facts, decisions, open questions and the things they are about.
Runs in your cloud
Reconcile
New knowledge is checked against what Merso already knows. Facts that changed are closed, not overwritten. Duplicates merge. Stale details expire. All of it follows rules you can read and edit.
Runs in your cloud, every day
Surface
Every session starts with a short briefing of what is current. Everything else is one search away, so the context stays small and precise.
Runs in your tools
Own
Merso runs in your own Cloudflare account. Your memory is readable, exportable and fixable, and it outlives any tool you use today.
Your account, your data
One memory for any AI app
Merso is a service, not a plugin. Anything that speaks MCP or HTTP can read and write it: coding agents, agent frameworks, chat apps, or an AI feature in your own product. Switch tools and your agents still remember.
Where it plugs in
- Claude Code
- Codex
- Pi
- Flue
- Pydantic AI
- Cursor
- Gemini CLI
- claude.ai
- ChatGPT
- Your own AI apps
How they connect
Where memory lives
Your Merso, in your Cloudflare account
- Journal of days
- Facts with time
- Things and how they relate
- Search by meaning
- The reconciler, daily, following constitution.md
The rules are a file
How a memory should be managed is a matter of opinion. Merso keeps that opinion in constitution.md, a plain-text file the reconciler follows. To change how your memory behaves, edit the rules, not the code.
constitution.md
# How this memory is managed ## Facts- Every fact has a start date. When it changes, close it.- Never overwrite. Keep the old value, answer with the current one. ## Things- Merge names that refer to the same thing. Keep the aliases. ## Forgetting- One-off details expire after 30 days unless something links to them.- Never store passwords, keys or tokens. ## Briefing- At most 60 lines. Only what is current.What Merso believes
- Saving is easy. Managing is everything.
- Capturing sessions is a solved problem. Deciding what is still true is the real work, so Merso is built around it.
- Memory belongs to you, not to your tools.
- One memory across harnesses and projects, in an account you control. Tools come and go; what you learned stays.
- Little in context, the rest on demand.
- A short briefing beats a long dump. Agents get sharper when they see less, and look up the rest when they need it.
- Facts have time.
- A memory should know what is true now, what used to be true, and when that changed.
- A person can read it and fix it.
- If you can’t see what your agent knows, you can’t trust it. Everything Merso remembers is readable and editable.
Roadmap
Built in public. Each stage is used daily by its author before it ships. The repository opens with v0.1.
Stage 1Designing now
Core and the first two harnesses
The memory service on Cloudflare, an MCP server, adapters for Claude Code and Codex, a daily journal and the briefing.
Stage 2
The reconciler
Facts with time, merged duplicates, relations between things and expiry. An adapter for Flue.
Stage 3
See and shape your memory
A browser for reading and correcting memory, weekly compaction, and more sources such as email and meeting notes.