Compare

A shared file is a good place to start.

CLAUDE.md, AGENTS.md and project notes can carry useful context between agents. The next question is who keeps those files current, consistent and appropriately accessible.

Keep the simple setup when it works.

Several agents can read the same file. They can also help update it. If your conventions change slowly and you are comfortable maintaining the workflow, a file may be all you need.

What grows with the work.

Updates

Capture the decisions made in conversations and reconcile conflicting edits.

History

Record what replaced an older decision, rather than simply accumulating both.

Access

Decide which client or project material each agent may reach and enforce it before retrieval.

A file, a workflow, or a service.

CapabilityShared context filesUnforgetter
Readable textYes; can be versioned in Git.Markdown source memory.
Used by several agentsYes, when they read the same files.A shared published memory over MCP.
Automatic updatesPossible with hooks, agents and a publishing workflow you maintain.Scoped Cloud capture and maintenance run in an internal Codex pilot; new-user setup remains guided.
Current versus supersededPossible if the file and update process record it.Temporal status is part of the source record and retrieval workflow.
Access boundariesDepend on filesystem permissions, sandboxing and your integration.Authorised collection and data-class restrictions in the Cloud service.
Operating the workflowYou choose and maintain the components.The service is being built to take on maintenance; alpha setup is guided.

Keep repository instructions next to the code.

Build commands, tests and repository conventions belong in CLAUDE.md or AGENTS.md. Project status, changed decisions and open questions can live in the memory you share across tools. The two approaches can work together.

Private alpha

Pick up where you left off.

Free during the private alpha. We help you connect your first agent.