Team memory for Codex

What Codex remembers today

• AGENTS.md: instructions Codex reads before it starts, from ~/.codex and from each directory between the Git root and where you work. The files are joined, and Codex stops adding them at 32 KiB by default.
• Memories: off by default. When enabled, Codex turns useful context from earlier chats into local memory files under ~/.codex/memories/, in the background.

OpenAI's own guidance is to keep required team guidance in AGENTS.md and treat memories as a helpful recall layer.

Where built-in memory stops

• AGENTS.md is written by hand and loaded whole. It holds standing instructions, and it is capped, so it has to stay small.
• Memories are local. They live in your Codex home directory and do not reach a teammate's Codex.
• Neither crosses tools. What Codex learns does not reach the same repository in Claude Code or Cursor.

AGENTS.md is still the right place for build commands and conventions. Most teams use both.

What Recallium adds to Codex

• Typed memories as the work lands: designs, decisions, root causes, fixes and runbooks, each linked to its files
• Search instead of load: before an edit, Codex searches by topic and file path and expands only the results it needs
• Shared with your team: on Cloud Pro, every teammate's agent reads and writes the repository's memory
• Shared with your other agents: the same memory in Claude Code, Cursor, GitHub Copilot and any MCP client
• Handoffs: workstreams, working state and session recap carry an effort across sessions and teammates

Add Recallium to Codex

1. Run the installer: npx -y recallium install finds Codex CLI and Codex Work, plus your other agents, and adds the MCP server
2. Sign in: the installer opens your browser to authenticate Codex; if that did not finish, run codex mcp login recallium
3. Check it: codex mcp list shows recallium as connected

Full steps are in the quickstart. Recallium Cloud is in a closed pilot; join the waitlist, or self-host the community edition.

Questions

Does Codex have memory?

Codex reads AGENTS.md files before every task, and it has an optional memories feature that stores local memory files from earlier chats. Neither is shared with teammates or other agents; an MCP memory server such as Recallium adds that.

AGENTS.md or Recallium?

AGENTS.md for the instructions Codex should follow every time. Recallium for the team's record: the decisions, root causes and fixes agents work out, searched when they are relevant.

Do Codex memories work with MCP?

Yes, separately. Codex can keep chats that used MCP tools out of its own memory generation (memories.disable_on_external_context); Recallium stores what the agent saves through MCP either way.