codex-history

You can export Codex conversation history to Markdown by running the CLI with an explicit session-id. The tool syncs history.jsonl during the export, ensuring your local session data remains consistent in both JSON and human-readable formats.

Yes, you can preview and archive Codex sessions directly from the command line. The CLI requires an explicit session-id for these actions and safely manages both active and archived data without operating outside your current project directory.

You list recent Codex CLI sessions by executing the history list command. This displays your active sessions and supports filtering to show all or archived records, providing output in either JSON or human-readable formats.

Deleting Codex conversation sessions locally is safe because the CLI enforces a strict, whitelisted command surface and uses force or confirm-like prompts. It requires an explicit session-id to prevent accidental data loss and keeps history.jsonl synchronized.

Codex history management works entirely through local Node.js scripts without external dependencies. It restricts operations to the current project directory, enforcing a strict command surface to prevent unintended modifications to your session archives.

Recovering an archived Codex session requires an explicit session-id to enforce strict, safe operations. This whitelisted command surface prevents accidental modifications and ensures history.jsonl remains synchronized when moving data between active and archived states.