ATLASO
LabPricing
Log inGet Started

Persistent memory for Codex

Codex starts fresh in every terminal session. Atlaso gives it continuity, recalling what you did last time before each prompt and capturing what changed after each turn, automatically. Codex Desktop installs the same plugin from its marketplace.

How it works

The Atlaso plugin installs hooks, an MCP server, and a memory skill into Codex. Recall runs before each prompt and capture after each turn, automatic in the CLI, and the same plugin installs in Codex Desktop through its marketplace and shared config.

What it installs: Hooks, MCP server, Skill.

01

Run one command

Paste the Atlaso install command in your terminal and pick Codex when it asks which tools should share your memory. Codex CLI and Codex Desktop share the same config, so one setup covers both.

02

Authorize this device

The browser opens to connect this device to your Atlaso account. About a minute, no API keys.

03

Keep shipping

Recall and capture run automatically from the next prompt on. Durable facts from one session are there in the next, even across projects and terminals.

Setup guide for Codex→

What it remembers

Yesterday's work, today

The refactor you started last session and the reasoning behind it, recalled at the start of the next one, in the same project or a different terminal.

Your shell and tooling choices

The test runner, the build command, the flags that finally worked, remembered so Codex reaches for your setup instead of guessing at it again.

Cross-project continuity

The conventions and preferences you carry between repos, so a new project in a fresh directory doesn't mean starting your memory over.

The decisions you don't want re-litigated

Why you chose one approach over another, kept so Codex builds on the decision instead of re-proposing the path you already dismissed.

Questions

01

Yes. Codex Desktop installs the same plugin from its marketplace, and because it shares Codex's config, connecting the CLI surfaces it in Desktop as well.

02

Yes, that's the point. Durable facts captured in one session are recalled in the next, even in a different project or a different terminal.

03

Yes. Keys and passwords are scrubbed on your device before anything is stored, and again on our servers. A memory is sent to a model only to produce your result, and kept nowhere afterwards. We never train on your memory and we never sell it. Forget a memory and it stops coming back in every tool, and if you want to leave, tell us and we delete your whole account.

Still have a question?

Write to us→

Other tools

The context Codex builds up follows you everywhere.

Atlaso keeps one memory, not one per app. Connect Codex and it draws from, and adds to, the same memory as every other tool you use. One tool on one device is free; Pro shares that one memory across as many tools and devices as you like.

Memory for Claude Code→Memory for Cursor→Memory for Claude Desktop→Memory for OpenCode→Memory for Antigravity→

Never explain twice

Connect Codex and what you decide today is there in tomorrow's session, and in every other tool you use.

Get Started
ATLASO

One memory for every AI tool you use.

Product

  • Pricing
  • Lab
  • Contact

© 2026 Atlaso Labs Inc. All rights reserved.

Legal & policies
Privacy PolicyTerms of ServiceCookie PolicyAcceptable UseRefundsDPASub-processors