Codex CLI memory

Codex CLI Memory: local project memory through hooks and MCP.

remem connects to Codex CLI with SessionStart and Stop hooks, then exposes project memory through MCP tools and CLI search.

Install for Codex CLI Codex setup
  • Codex hooks
  • MCP registration
  • Strict duplicate gating
  • Local database
codex - remem

$ remem install --target codex

ok Codex MCP server registered

ok Codex hooks configured

$ remem search "review threads"

decision green CI alone is not enough

preference separate remote truth from local state

auditable recall available mid-session

How it helps Codex

Codex gets continuity without a hosted memory service.

The same local store powers automatic session injection, MCP search, manual saves, workstreams, and timelines.

01

Session context

SessionStart injects compact memories and preferences.

02

Stop summaries

Stop hooks summarize durable lessons in the background.

03

MCP tools

Codex can call `search`, `save_memory`, `timeline`, and workstream tools.

04

Local audit

`remem why`, status, and usage commands make recall inspectable.

Install

Connect remem to Codex CLI.

Install the binary, configure Codex hooks and MCP, then restart Codex.

brew install majiayu000/tap/remem
remem install --target codex
remem doctor
remem search "last decision"

FAQ

Common Codex CLI memory questions.

ScopeProject

Memory is project-scoped so unrelated repositories do not leak into recall.

ToolsMCP

Codex can retrieve memories mid-session through remem MCP tools.

NoiseGated

Codex uses strict duplicate-injection gating to avoid repeated startup output.