Use Claude Code's project memory in Codex with recall

When I switch from Claude Code to Codex in the same repo, I want Codex to know the project's ground rules before it edits anything. Claude Code stores those notes as Markdown. I built recall so another agent can read the same files over MCP.

Get your first memory back

You'll need Node.js 18 or later and a repo where Claude Code has already saved some project memory. Choose a project whose notes you're comfortable sharing with the receiving agent. Replace the example path with the absolute path to that repo.

codex mcp add recall -- npx -y @fainir/recall@0.3.0 --claude-code "/path/to/your/repo" --read-only

Open a new Codex session and ask it to call recall's memory_list for this project. Pick a relevant note and ask it to read that note with memory_recall. The first useful result is a project rule you can confirm, such as which integration test to run.

I tested the command from a clean profile with two sample notes. The first told the agent to run the integration suite and linked to a second note about the test setup. One call returned both.

> memory_recall {"requires": ["feedback_testing"]}
## feedback_testing
Run npm run test:int. The fixture setup is in [[reference_ci]].

## reference_ci
Use the sample database postgres://sample:[redacted]@db.example.test/fixtures.

That's a shortened result from the fixture. recall followed the wiki link and hid the sample password in the returned text. Both Markdown files stayed intact. recall 0.3.0 release notes.

How it works

recall finds the project's Claude Code memory directory from its Git root. A worktree uses the main checkout's memory. The server reads the existing Markdown files directly and follows links from the notes you name within a token budget.

--read-only offers memory_list, memory_get, memory_recall, and memory_due. If you enable writes, recall can also update notes in Claude Code's format. Claude Code reads the updated notes in a later session.

The Codex command saves a user-level MCP entry. It keeps pointing to the chosen repo when you open other projects. Version 0.3.0 masks recognizable credentials in tool replies by default. Review the notes you share because the rest of their text can reach the receiving agent's model provider.

For Cursor, add the same command and arguments to your project's .cursor/mcp.json.

{
  "mcpServers": {
    "recall": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@fainir/recall@0.3.0", "--claude-code", "/path/to/your/repo", "--read-only"]
    }
  }
}

The project README has the Gemini CLI and Cline setup, plus the JavaScript API. Get recall and see the setup guide.