Provider

Codex CLI

OpenAI's Codex CLI writes JSONL session logs. Budi tails these the same way it handles Claude Code transcripts — automatic discovery, real-time attribution.

Live since v8.3.0

Data sources

Local JSONL session logs (primary)

Codex CLI writes JSONL session logs that contain structured conversation data including token usage, model information, and tool invocations. Budi auto-discovers and tails these files.

Path: ~/.codex/sessions/

What's parsed

Input and output token counts per message
Model name and version (e.g. codex-mini, o4-mini)
Dollar cost (computed from token counts via budi's pricing manifest)
Session boundaries and timestamps
Repo and branch context from the working directory

Caveats

Zero-config provider

Like Claude Code, Codex CLI is zero-config — budi auto-discovers the session log directory and starts tailing immediately.

Cost is computed from token counts using budi's pricing manifest, not from OpenAI's billing API. If your org has custom pricing, the numbers may differ.
Codex CLI's session log format has changed across versions — budi supports the current format and the previous major version.

How to verify

After installing budi, run a Codex CLI session. Then:

budi doctor

Look for the Codex CLI tailer in the output:

✓ Daemon running (pid 12345, port 7878)
✓ Codex CLI tailer: active
  Path: ~/.codex/sessions/
  Last event: 5s ago
✓ All checks passed.

To see Codex CLI spend:

budi stats projects --filter codex