Every session starts from zero.
Architecture, commands, conventions, and decisions live in the last conversation. The next agent never saw it.
OPEN SOURCE / CODEX + CLAUDE CODE + OPENCODE
THE MEMORY GALLERY
mem-sync gives Codex, Claude Code, and OpenCode one canonical project memory. A single Markdown file, symmetric writes, and conflict-safe reconciliation — local-first.
PUBLIC RELEASE / 18 NOV 2026CA COMING SOON◈ PROJECT / THE PROBLEM
Architecture, commands, conventions, and decisions live in the last conversation. The next agent never saw it.
AGENTS.md and CLAUDE.md fall out of sync. Codex, Claude Code, and OpenCode stop sharing the same truth.
The why behind the code is the most expensive thing to reconstruct. Most of it is never written down.
“The most expensive token is the context you keep re-sending.”
◈ PROTOCOL / THE SYNC
mem-sync does not make one harness authoritative. It makes the project memory portable, symmetric, and auditable.
Any supported agent can write. No harness is authoritative and no source silently wins.
Concurrent edits are preserved in a labeled union. Originals stay in .mem-sync/conflicts/.
mem-sync off stops propagation and keeps the latest bytes. Leave without losing the record.
Plaintext Markdown on your machine. No cloud account required. No credentials in memory.
WHAT MEM-SYNC ON DOES
Resolves the exact project root. It never enables an ancestor.
Backs up existing instruction and Claude memory files under .mem-sync/backups/.
Neutrally merges AGENTS.md, CLAUDE.md, and Claude MEMORY.md. Each source is labeled; no source wins.
Adds the versioned shared-memory protocol for remember, forget, and cleanup.
Hard-links AGENTS.md and CLAUDE.md to .mem-sync/memory/MEMORY.md.
Links Claude auto-memory at the Git root and registers the project for reconciliation.
PROJECT STATE
.mem-sync/ ├── memory/ │ ├── MEMORY.md │ ├── codex/<thread-id>.md │ └── <claude-topic>.md ├── state.json ├── backups/ ├── conflicts/ └── migrations/
All project-owned. Plaintext. Reversible with mem-sync off.
◈ PROOF / THE CODE
mem-sync is MIT-licensed, local-first, and designed to be read. The canonical memory is plaintext. The conflict history is kept. The tool works without the token.
Real terminal shape from the supported status surface. Values are illustrative; your project path and adapter state will differ.
$ mem-sync status { "enabled": true, "root": "/dev/agent", "surfaces": { "AGENTS.md": { "exists": true, "hardlinked": true }, "CLAUDE.md": { "exists": true, "hardlinked": true } }, "adapters": { "codex": { "instruction_surface": "AGENTS.md", "native_memory_harvest": true }, "claude-code": { "instruction_surface": "CLAUDE.md", "native_memory_linked": true }, "opencode": { "instruction_surface": "AGENTS.md", "live_instruction_updates": true } }, "shadowing_files": [] }_
git clone https://github.com/anabologyco-maker/mem-sync.git /opt/mem-sync sudo ln -s /opt/mem-sync/bin/mem-sync /usr/local/bin/mem-sync mem-sync --version
Credentials, hidden system prompts, permission policy, and arbitrary transcripts are out of scope.
The canonical memory is a file on your machine. No cloud account is required.
mem-sync off stops propagation and preserves the latest bytes. Nothing is rolled back.
◈ REFERENCES / SOURCES
Source, issues, tests, and the complete implementation.
github.com/anabologyco-maker/mem-sync ARCHITECTUREArchitectureData flow, state layout, conflict policy, and design goals.
docs/architecture.md MEMORY SYSTEMSMemory-system mapPrecedence research for Codex, Claude Code, and OpenCode.
docs/memory-systems.md READMEInstall and commandsQuick start, merge semantics, session migration, and limits.
README.md LICENSEMIT LicenseOpen source, inspectable, and reusable.
LICENSE CODEXAGENTS.md instructionsOfficial Codex project-instruction documentation.
learn.chatgpt.com CODEX MEMORIESLocal memoriesOfficial Codex memory documentation.
learn.chatgpt.com CLAUDE CODEProject memoryOfficial Claude Code memory documentation.
code.claude.com OPENCODEInstructionsOfficial OpenCode instruction documentation.
opencode.aiResearch baseline 2026-08-26, as documented in the repository. Upstream behavior can change. The repository and vendor docs are the authoritative source.
◈ PUBLIC RELEASE / 18 NOV 2026
mem-sync is releasing to the public.
The project is open source, local-first, and built for Codex, Claude Code, and OpenCode. The gallery is the public record: architecture, commands, proof, and references.
MEMS ($MEM) is the token that accompanies the release. It is not required to use the software. The official CA will be published here at public release.
TOKEN / OPTIONAL
The CA is published only on memsync.gallery. It is never sent by DM. Verify every character before trading.
PUBLISHES AT PUBLIC RELEASEThe official CA will appear here at public release. It is published only on memsync.gallery and never sent by DM.
◈ ROADMAP / WHAT COMES NEXT
Codex, Claude Code, and OpenCode share one canonical memory. MIT-licensed, local-first, and reversible.
More agent harnesses and integration patterns, funded through the project.
A public directory of memory-compatible tools, patterns, and integration notes.
Curated memory cards, exhibits, and open-source bounties.
◈ THE CURATOR / GALLERY KEEPER
MEMS is the keeper of the gallery and the face of the public release. The project is mem-sync; MEMS is how the gallery signs the record.
It does not trade. It remembers. It keeps the decisions, the commands, and the architecture that your agents should never lose.
One source of truth. No silent winner.
Durable facts survive the session.
Cleanup is a write, not a conflict.
“You can forget. MEMS won't.”
◈ VISITOR INFORMATION
mem-sync is a local-first Python tool that gives Codex, Claude Code, and OpenCode one project-scoped memory. It makes one canonical Markdown file at .mem-sync/memory/MEMORY.md and links the supported agent surfaces to it.
Codex, Claude Code, and OpenCode. The architecture is deliberately harness-neutral: any supported surface can write, and no surface is treated as the winner.
No. mem-sync is local-first. The canonical memory is plaintext Markdown on your machine. The project explicitly avoids copying credentials, hidden system prompts, permission policy, and arbitrary transcripts into shared memory.
mem-sync keeps both versions in a labeled neutral union and saves the originals under .mem-sync/conflicts/. It does not pick a silent winner. A human can then clean up the record.
Yes. The project is MIT-licensed and has no runtime dependencies beyond Python 3.10+. The source, tests, architecture notes, and research baseline are public.
The public release makes the project site, architecture, references, and official CA public on 18 November 2026 at 01:13 UTC. The release is the project milestone; the token is a secondary detail.
MEMS is the token that accompanies the public release. It is not required to use the software. The project is the product; the token is a secondary release detail.
No. mem-sync runs locally and works without the token. The token accompanies the release; it does not gate the software.
The public release is targeted for 18 November 2026 at 01:13 UTC. The contract address will be published only on memsync.gallery at release.
No presale, no private round, no claim, and no wallet-connect step. Anyone offering early access or a migration tool is not us.
No. The token is a digital asset with no promise of financial return. Digital assets are volatile and speculative. Never risk more than you can afford to lose. Do your own research.