Tracing for the Codex CLI records each prompt as a trace, with the tools it invoked nested beneath it. Codex needs one extra approval step after installing, which this page covers.

​
Install

On macOS or Linux:
On Windows:
The installer prompts for your license key and project name, stores them in ~/.atatus/harness/config.json, and registers the hook entries in ~/.codex/config.toml. Add --with-skills to also link the manage-codex-tracing skill into the current directory.

​
Approve the hooks

Codex requires you to approve hooks before they run. After installing, start Codex and run:
Until you approve the hooks, Codex does not run them and no traces are sent. This is a one-time step per user account, and it is the most common reason a Codex install looks like it failed.

​
What gets captured

Codex reports token usage through a separate channel from its hooks. The installer registers a notify entry alongside the hooks to pick that up, so turns carry token counts and cost.

​
Where things live

Six hook events are handled: SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, PermissionRequest, and Stop. Token usage arrives separately via agent-turn-complete.
~/.codex/atatus-env.sh is where the installer puts environment overrides for Codex specifically. Use it if you want Codex traced differently from your other tools, rather than editing your shell profile.

​
Uninstall

This removes the hook entries and the notify entry from ~/.codex/config.toml. See Uninstall for the full-wipe option.