cd /news/ai-tools/codex-token-usage-by-model · home › topics › ai-tools › article
[ARTICLE · art-166467] src=usageatlas.com ↗ pub= topic=ai-tools verified=true sentiment=· neutral

Codex token usage by model

UsageAtlas published a guide showing how to break down Codex token usage by model, using the model metadata recorded in each Codex session file to split input, cached, output and reasoning tokens per model. The guide recommends sorting models by total tokens and then by tokens per request over a 30-day range in UsageAtlas's Insights view, then rewriting prompts on the highest tokens-per-request model to pass file ranges instead of whole files. UsageAtlas argues the per-model split reveals why usage happened, since reasoning models bill more output tokens for the same visible answer and a small model used for exploration can drive a large share of requests without a large share of cost.

read3 min views24 publishedNov 7, 2026
Codex token usage by model
Image: Usageatlas (auto-discovered)

Quick answer #

Each Codex session file records the model used for the turn. Grouping those records by model gives input, cached, output, and reasoning tokens per model. UsageAtlas does this automatically in its Insights view; the model you use for exploration usually produces the most requests, while the strongest model produces the most tokens per request.

Get the model into the total #

A total token count hides the decision that caused it. Model is the most useful split because it is the variable you control before a task starts.

Metric What it tells you What to do with it
Requests per model Where the volume is Move repetitive work to a cheaper model
Tokens per request How heavy each call is Trim context on the heaviest model
Output share How much the model writes Ask for diffs instead of essays
Cached share How much prompt reuse you get Keep a stable prefix across turns

The pattern most people find #

Small models win on request count and lose on tokens per request only if you feed them a large context. In practice the expensive line is often the model you use for long refactors with the whole repository in view.

  • Exploration: many small requests, low tokens each.
  • Implementation: fewer requests, larger context.
  • Debugging loops: repeated context, highest waste.
  • Review passes: output-heavy, cheap if the diff is the only input.

Turn the split into a decision #

  1. Open Insights in UsageAtlas and select a 30-day range.
  2. Sort models by total tokens, then by tokens per request.
  3. Pick the model with the highest tokens per request and find its top sessions.
  4. Rewrite those prompts to pass file ranges instead of whole files.
  5. Recheck after a week; the split should shift without changing your workflow.

Why the model split matters more than the total #

A single total tells you how much you used. The per-model split tells you why. Reasoning models bill more output tokens for the same visible answer, and a small model used for exploration can account for a large share of requests without accounting for a large share of cost. Reading the split is the difference between cutting volume and cutting the wrong volume.

  • High reasoning-model share with few tasks: long thinking per task.
  • High small-model share with many tasks: exploration and retries.
  • Flat split across models: you are switching manually, so compare per task.
  • One model dominating: that is the default to review first.

For the cost side of the same split, see Codex cost per project, and for the counting rules see how Codex counts tokens.

Questions, answered #

Does Codex record which model each request used?

Yes. Session files include model metadata for the turn, which is what makes a per-model breakdown possible.

Why is the cheaper model showing more tokens?

You probably send it a larger context or use it for more requests. Compare tokens per request, not just the total.

Can I see the model split for one project?

Yes, if the tracker groups sessions by working directory. UsageAtlas reads the directory from the session record, so project and model can be combined.

── more in #ai-tools 4 stories · sorted by recency
── more on @codex 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/codex-token-usage-by…] indexed:0 read:3min 2026-11-07 · —