Codex + Ambience.
Updated 2026-06-07 · Shared agent memory
Shared memory for Codex sessions, with scoped context at start and durable capture when work lands.
Ambience helps Codex stop repeating context work by making prior team decisions, conventions, and failure modes available through governed memory.
Session start context
Codex can begin a session with a compact Ambience memory summary and task-relevant context. The goal is to make the first command smarter, not to flood the prompt.
MCP and CLI access
Ambience exposes search, read, save, and admin-preview workflows through MCP and CLI surfaces. That keeps Codex aligned with the same memory actions available in the app.
Durable saves
When a decision, convention, failure, or skill lands, Codex can save it to Ambience immediately. Future agents then inherit the result instead of reverse-engineering it from git history.