What happens if I import the same rollouts twice?

Nothing is duplicated. Identical chats are kept as-is; changed chats you have not touched in idapt are updated in place; changed chats you touched are left alone.

Which Codex versions are supported?

Rollouts from Codex CLI 0.42.0 and newer import cleanly (the rollout format under ~/.codex/sessions). Unknown record types are skipped with a visible count.

Bring your Codex CLI chats

One command reads Codex CLI's rollouts and imports them with dates and tool calls: `idapt chat import --from codex`.

How to migrate

1
Install the CLI
One global install; the same CLI the quickstarts use.
```
npm i -g @idapt/cli
```
```
npm i -g @idapt/cli
```
2
Import your chats
Run the importer. It signs you in if needed (browser), scans ~/.codex/sessions (CODEX_HOME honored), and previews what will be imported. Default scope: sessions started in the current directory; use --all for every project on the machine.
```
idapt chat import --from codex
```
```
idapt chat import --from codex
```
3
Keep Codex while you evaluate
Point Codex at idapt's endpoint and compare on your real workload before you switch fully.
Quickstart

What moves

Codex CLI	In idapt	How
Rollout history in scope	Chats in the workspace, source dates preserved	Automatic
Function calls + outputs	History rows; folded into text when a model replays them and never re-executed	Automatic
Reasoning streams	Not imported in v1 (text and tools are)	No equivalent

FAQ

Help Center: Import chats from coding agents Quickstart: Codex CLI

Install the CLI