Integrations · Agents
Track Codex CLI cost by project and ticket.
Codex CLI pushes its usage over OpenTelemetry, and the Token Controller CLI reads its session files. Together they put Codex cost on tickets, with a summary of each session.
- DoorsTelemetry push, session files through the CLI
- Brings inTokens, cost, model, person, repository, branch
- Cost lands onProjects by repository, tickets with the CLI
Two doors, counted once.
When telemetry and a token entry describe the same session, they are joined by session and message ID and counted once.
- 1
Push telemetry
Point Codex CLI's OpenTelemetry exporter at your organization's ingest URL, with the organization token.
- 2
Read session files
The CLI reads Codex session files with the open source ccusage adapters. Reading the same files twice changes nothing.
- 3
Review and submit
Agent managers check their draft token entries and submit their token sheet.
What telemetry carries.
Numbers and identifiers only
Tokens, cost, model, person, repository, and session and message IDs. No prompt text.
Local first
Without a connected service the CLI keeps everything on your machine, places token entries with your personal rules and exports CSV.
Against the OpenAI bill
At the close, Codex cost is checked against the bill read from OpenAI's Costs API.
In the docs
Start alone in a few minutes. Add your team when the first month closes.
No card for the free plan. Fourteen days to try the Team plan.