OPEN SOURCE / CODEX + CLAUDE CODE + OPENCODE

MEM-SYNC

THE MEMORY GALLERY

ONE MEMORY.
EVERY AGENT.

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
VERSION
v0.2.1
LICENSE
MIT
RUNTIME
PYTHON 3.10+
SURFACES
3 AGENTS
EXHIBIT 001 / SHARED MEMORYPERMANENT COLLECTION
MEMS the Curator, a framed memory robot with a glowing cyan face and a brass gallery frameCL-001 / 2026
MEMS / THE CURATORACQUIRED 2026
MEMSYNC.GALLERYOPEN SOURCE / MIT

◈ PROJECT / THE PROBLEM

EVERY AGENT
STARTS FROM ZERO.

01CONTEXT LOST

Every session starts from zero.

Architecture, commands, conventions, and decisions live in the last conversation. The next agent never saw it.

02INSTRUCTIONS DRIFT

Each surface follows a different rulebook.

AGENTS.md and CLAUDE.md fall out of sync. Codex, Claude Code, and OpenCode stop sharing the same truth.

03DECISIONS FORGOTTEN

The reasoning disappears with the session.

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

ONE CANONICAL
MEMORY.

CANONICAL MEMORYMEMORY.md.mem-sync/memory/AGENTS.mdCODEX / OPENCODEREAD + WRITE / SAME INODECLAUDE.mdCLAUDE CODEREAD + WRITE / HARD LINKCODEX HARVESTGENERATED MEMORYREAD-ONLY / WATERMARKEDCLAUDE MEMORYAUTO-MEMORY DIRSYMLINK / GIT ROOT

mem-sync does not make one harness authoritative. It makes the project memory portable, symmetric, and auditable.

01
SYMMETRIC

Any supported agent can write. No harness is authoritative and no source silently wins.

02
CONFLICT-SAFE

Concurrent edits are preserved in a labeled union. Originals stay in .mem-sync/conflicts/.

03
REVERSIBLE

mem-sync off stops propagation and keeps the latest bytes. Leave without losing the record.

04
LOCAL-FIRST

Plaintext Markdown on your machine. No cloud account required. No credentials in memory.

WHAT MEM-SYNC ON DOES

  1. 01

    Resolves the exact project root. It never enables an ancestor.

  2. 02

    Backs up existing instruction and Claude memory files under .mem-sync/backups/.

  3. 03

    Neutrally merges AGENTS.md, CLAUDE.md, and Claude MEMORY.md. Each source is labeled; no source wins.

  4. 04

    Adds the versioned shared-memory protocol for remember, forget, and cleanup.

  5. 05

    Hard-links AGENTS.md and CLAUDE.md to .mem-sync/memory/MEMORY.md.

  6. 06

    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.

THE FIRST TWO MOVES$ mem-sync on$ mem-sync status$ mem-sync offREAD THE README

◈ PROOF / THE CODE

REAL TOOL.
REAL 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.

MIT LICENSEv0.2.1PYTHON 3.10+NO RUNTIME DEPS3 ADAPTERS

Real terminal shape from the supported status surface. Values are illustrative; your project path and adapter state will differ.

mem-sync / statusLOCAL
$ 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": []
}_
INSTALL FROM SOURCEREAD THE INSTALL NOTES
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
NEVER SYNCEDSECRETS STAY LOCAL

Credentials, hidden system prompts, permission policy, and arbitrary transcripts are out of scope.

LOCAL-FIRSTPLAINTEXT MARKDOWN

The canonical memory is a file on your machine. No cloud account is required.

REVERSIBLEOFF IS A REAL EXIT

mem-sync off stops propagation and preserves the latest bytes. Nothing is rolled back.

◈ PUBLIC RELEASE / 18 NOV 2026

RELEASING
TO THE PUBLIC.

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

TICKER
$MEM
CHAIN
SOLANA
CA
COMING SOON
DEX
PROFILE AT $500K
NO PRESALENO CLAIMNO WALLET CONNECT

The CA is published only on memsync.gallery. It is never sent by DM. Verify every character before trading.

CA / SOLANACOMING SOON
PUBLISHES AT PUBLIC RELEASE

The official CA will appear here at public release. It is published only on memsync.gallery and never sent by DM.

PUBLIC RELEASE / T-MINUS18 NOV 202601:13 UTC
MEMS releases to the public on 18 NOV 2026 at 01:13 UTC. The visual countdown is updating live.

◈ ROADMAP / WHAT COMES NEXT

THE PROJECT
KEEPS MOVING.

SYNC 01NOW

CORE

Codex, Claude Code, and OpenCode share one canonical memory. MIT-licensed, local-first, and reversible.

SYNC 02NEXT

ADAPTERS

More agent harnesses and integration patterns, funded through the project.

SYNC 03LATER

REGISTRY

A public directory of memory-compatible tools, patterns, and integration notes.

SYNC 04ONGOING

GALLERY

Curated memory cards, exhibits, and open-source bounties.

MEMS the Curator, the framed memory robot mascot of the MEMS galleryTHE CURATOR / CL-001

◈ THE CURATOR / GALLERY KEEPER

MEET
MEMS.

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.

01KEEPS THE CANON

One source of truth. No silent winner.

02NEVER FORGETS

Durable facts survive the session.

03HATES STALE CONTEXT

Cleanup is a write, not a conflict.

“You can forget. MEMS won't.”

◈ VISITOR INFORMATION

READ BEFORE
YOU ENTER.

01What is mem-sync?

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.

02Which agents are supported?

Codex, Claude Code, and OpenCode. The architecture is deliberately harness-neutral: any supported surface can write, and no surface is treated as the winner.

03Is my project memory uploaded?

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.

04What happens when two agents edit memory at once?

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.

05Is mem-sync free and open source?

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.

06What is the public release?

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.

07What is MEMS ($MEM)?

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.

08Does the token power mem-sync?

No. mem-sync runs locally and works without the token. The token accompanies the release; it does not gate the software.

09When is the public release?

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.

10Is there a presale or claim?

No presale, no private round, no claim, and no wallet-connect step. Anyone offering early access or a migration tool is not us.

11Is this financial advice?

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.