Atlaso Memory for Codex

Automatic long-term memory for OpenAI Codex. Atlaso recalls relevant context before each prompt, captures durable facts and decisions as you work, and syncs across your sessions and devices — for the CLI, the IDE extension, and the Desktop app (they share one config, so a single install covers all three).

• 🧠 Recall — relevant past context is injected before Codex answers.
• 📝 Capture — durable decisions, preferences, and gotchas are saved as you work.
• 🔒 Local-first — memory works offline on your machine; sign in to sync to the cloud.
• 🗂️ Personal + project memory — preferences follow you everywhere; repo facts stay in the repo.

Why this exists

Codex reads AGENTS.md and keeps its own local memories on the machine you run it on. This connector gives Codex CLI, IDE and Desktop a memory that carries yesterday's work into today, your shell and tooling choices, and the decisions you don't want re-litigated, and shares it with Claude Code, Cursor and your other tools. Automatic in Codex CLI; Codex Desktop installs the same plugin from its marketplace. How it works · Docs

Install

Install uv first. The plugin runs on a uv-managed Python, so uv is the only prerequisite. Without it, prompts run without recall and Codex shows "Atlaso needs uv. Install uv, then retry your prompt; memory will set up in the background."

Codex Desktop / IDE (GUI)

1. Open Codex → Plugins.
2. Click + (top right) → Add marketplace.
3. Fill in:
   • Source: atlaso-labs/codex
   • Git ref: main
   • Sparse paths: (leave blank)
4. Click Add marketplace, then open Atlaso and Add to Codex on the Atlaso Memory plugin.
5. Right after an install or update the plugin prepares its memory runtime in the background, which can take a few minutes. Until it is ready, prompts run without recall and Codex shows a notice saying so. The first prompt after it is ready opens a browser to connect your account (optional — memory works locally without it). With the Atlaso CLI, atlaso setup prepares the runtime up front and atlaso status says whether your next prompt gets recall.

Codex CLI

codex plugin marketplace add atlaso-labs/codex
codex plugin add atlaso@atlaso

What gets installed

Piece	Mechanism	What it does
recall	UserPromptSubmit hook	injects recalled memory before Codex sees your prompt
capture	Stop hook	saves the finished exchange (instant local write, synced later)
start	SessionStart hook	eligible personal + current-project Ambient Memory, then background cache sync
memory tools	MCP server — recall, remember, forget, recent, status	deliberate, model-invoked memory
skill + rules	SKILL.md + AGENTS.md	when to remember, personal vs project, fixing memory

Recalled memory is injected as a plain branded block — no instructions, the model decides how to use it:

=== Atlaso Memory ===
- recalled note
- recalled note
=== Atlaso Memory ===

Hooks fail open: any error → silent no-op, your turn proceeds. Free plan = local-only; paid = cloud sync across devices.

Privacy

Memory is stored locally on your machine by default. Cloud sync is opt-in (sign in). Learn more at atlaso.ai.

Note for Codex Desktop

A past Desktop update temporarily stopped hooks from firing (openai/codex#21639). If automatic recall/capture seems quiet on Desktop, the model-invoked memory tools (MCP) still work. Set ATLASO_DEBUG=1 and check ~/.atlaso/atlaso-codex-*.log to confirm hooks fire.

---

Built by Atlaso Labs Inc. · source: github.com/atlaso-labs/codex

Ambient Memory at session start

When enabled on an eligible plan, the start hook requests a brief for this tool and the host event's project directory. Personal context can accompany the current project's context. Missing or untrustworthy project identity requests personal context only. A first session can receive a brief without a local cache. Each session validates the current server policy; disabled, offline, rejected, or incompatible responses inject no Ambient Memory. Reopening after recovery retries automatically. Per-turn recall remains a separate feature.

The Python start path has a three-second budget on POSIX; the host hook manifest sets a five-second timeout, including runtime startup. The latter is also the Windows bound. First-time runtime installation can exceed that budget and yield no brief until dependencies are available. These source changes require publishing the rebuilt plugin and updating the installed version; a source checkout alone does not update a user's plugin. Host versions must actually execute SessionStart.