MemoryRouter
Fix

AI forgets what you told it yesterday

Yesterday you explained the constraint, agreed on an approach, and it worked. Today the same tool is cheerful, competent, and unaware that any of it happened. That is not a mistake. It is how sessions are built.

Sources checked 2026-09-25.

Why yesterday is gone

A session is a context window. The model has no memory of Tuesday unless something puts Tuesday into today’s window: a file, a summary, or an external store.

Products have started adding memory layers. Claude builds memory topics across chats, ChatGPT keeps saved memories and can reference chat history, and coding agents read instruction files. Each of those helps inside one product, and each stops at that product’s edge.

So the answer to "why does it forget" is mechanical: sessions end, context windows refill, and instruction files carry standards rather than history.

Free fixes you can do today

These work today, with no new tools.

  1. 1

    Write it down in the place your tool reads

    CLAUDE.md for Claude Code, AGENTS.md for Codex and OpenCode, rules files for editors. One line per decision, dated, in the file the tool loads first.

  2. 2

    Start sessions with a three-line brief

    "Where we are, what changed, what is next." It costs less than a paragraph and prevents an hour of re-derivation.

  3. 3

    Keep the brief growing in one file

    One decisions file per project beats a folder of notes nobody reads. Prune it monthly.

  4. 4

    Do not depend on a single tool for memory

    Whatever you rely on should be readable by more than one assistant, because your toolchain will change before your project ends.

The durable fix

The durable answer is a memory store that lives outside any single assistant and holds decisions with dates and context. MemoryRouter provides that store, plus the integrations that make it automatic where hooks exist.

The result: tell it once, in any connected tool, and the next session, the next day, and the other tool all start with it.

  1. 1

    Install where it can be automatic

    Claude Code and Codex

    npx -y memoryrouter-claude init
    npx -y memoryrouter-codex init --scope user
  2. 2

    Connect the rest over MCP

    Cursor, Windsurf, Cline, Zed, Continue, and other MCP clients share the same vault, and Claude and ChatGPT connect through connectors.

Full setup guide: Claude Code setup guide

Get a memory key

Three minutes to install, 14 days free, then $20 per month.

Related

FAQ

Sources

Sources checked 2026-09-25. Tool behavior changes; check the vendor docs before relying on a detail.

Start free