codex - 💡(How to fix) Fix Regression: Token usage significantly increased in v0.121.0 vs v0.116.0 for identical prompt and unchanged workspace [5 comments, 4 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18345Fetched 2026-04-18 05:55:31
View on GitHub
Comments
5
Participants
4
Timeline
14
Reactions
1
Timeline (top)
commented ×5labeled ×5closed ×1cross-referenced ×1
  • v0.116.0 → best efficiency (lowest input, cached, and reasoning)
  • v0.115.0 → moderate usage
  • v0.121.0 → clear regression (highest across all metrics)

Root Cause

  • v0.116.0 → best efficiency (lowest input, cached, and reasoning)
  • v0.115.0 → moderate usage
  • v0.121.0 → clear regression (highest across all metrics)

Code Example

v0.115.0
total=63,395
input=60,290 (+570,368 cached)
output=3,105
reasoning=813

v0.116.0  (most efficient)
total=52,896
input=50,392 (+333,056 cached)
output=2,504
reasoning=548

v0.121.0  (regression)
total=86,194
input=83,231 (+673,664 cached)
output=2,963
reasoning=1,040
RAW_BUFFERClick to expand / collapse

What issue are you seeing?

After upgrading OpenAI Codex from v0.116.0 to v0.121.0, token usage increased significantly (by ~60%+) for the exact same prompt, executed in the same workspace, with no code or configuration changes.

Interestingly, v0.116.0 appears to be the most efficient version, while both v0.115.0 and v0.121.0 use substantially more tokens. This suggests a regression in context handling introduced after v0.116.0.

Environment Codex versions tested: v0.115.0 v0.116.0 v0.121.0 Model: gpt-5.3-codex medium OS: Windows Workspace: same project, no changes between runs Prompt: identical in all cases

What steps can reproduce the bug?

Open the same project workspace Run Codex with version v0.115.0

Ask: Please summary me the code within the workspace Note token usage Repeat with: v0.116.0 v0.121.0 Ensure: no changes to code no changes to configuration same prompt used

What is the expected behavior?

Token usage should remain relatively stable across versions for the same prompt and workspace, or change only slightly due to minor improvements.

Additional information

Actual Behavior

Token usage varies significantly between versions:

v0.115.0
total=63,395
input=60,290 (+570,368 cached)
output=3,105
reasoning=813

v0.116.0 ✅ (most efficient)
total=52,896
input=50,392 (+333,056 cached)
output=2,504
reasoning=548

v0.121.0 ❌ (regression)
total=86,194
input=83,231 (+673,664 cached)
output=2,963
reasoning=1,040

Summary

  • v0.116.0 → best efficiency (lowest input, cached, and reasoning)
  • v0.115.0 → moderate usage
  • v0.121.0 → clear regression (highest across all metrics)

extent analysis

TL;DR

Downgrade to OpenAI Codex v0.116.0 to mitigate the significant increase in token usage.

Guidance

  • Verify that the issue persists across different prompts and workspaces to rule out any specific prompt or workspace-related causes.
  • Compare the configuration and model settings between v0.116.0 and v0.121.0 to identify any potential changes that may be contributing to the regression.
  • Test intermediate versions between v0.116.0 and v0.121.0 to pinpoint the exact version where the regression was introduced.
  • Consider reaching out to OpenAI support for further assistance, as the issue may be related to changes in the Codex algorithm or model.

Example

No code snippet is provided as the issue is related to the OpenAI Codex version and configuration.

Notes

The issue may be specific to the gpt-5.3-codex medium model, and testing with other models may yield different results. Additionally, the regression may be due to changes in the Codex algorithm or model, which may not be immediately apparent from the version change.

Recommendation

Apply workaround: Downgrade to v0.116.0, as it has been identified as the most efficient version, and the issue is likely due to a regression introduced in later versions.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Regression: Token usage significantly increased in v0.121.0 vs v0.116.0 for identical prompt and unchanged workspace [5 comments, 4 participants]