codex - 💡(How to fix) Fix Codex CLI burns subscription tokens when only checking /status repeatedly [3 comments, 3 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#22040Fetched 2026-05-11 03:20:22
View on GitHub
Comments
3
Participants
3
Timeline
7
Reactions
0
Author
Timeline (top)
labeled ×4commented ×3
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

codex-cli 0.130.0

What subscription do you have?

Plus

What platform is your computer?

Linux 6.8.0-111-generic x86_64 x86_64

What issue are you seeing?

What happened: Codex CLI appears to deplete usage limits even when no real work is done. I checked /status a few consecutive times and saw my 5h limit drop significantly.

Example:

  • 3 consecutive /status checks
  • about 12% of my 5h limit gone
  • no coding task, no file changes, no tool work

Environment:

  • Codex CLI version: codex-cli 0.130.0
  • OS: Linux 6.8.0-111-generic x86_64 x86_64
  • Plan/subscription: Plus
  • Model: gpt-5.5
  • Install method: npm

Notes: I also burned through my weekly limit in four ~5h sessions, so I’m trying to understand if idle/status usage is being counted unexpectedly.

What steps can reproduce the bug?

  1. Start Codex CLI
  2. Run /status
  3. Run /status again
  4. Run /status again
  5. Observe usage limit decrease

What is the expected behavior?

Checking /status should not consume meaningful usage, or at least the usage cost should be clearly explained.

Additional information

I burned through my weekly limit in four ~5h sessions, so I’m trying to understand if idle/status usage is being counted unexpectedly.

Additional Datapoint:

no file edits, no shell commands, no task execution between those checks. <img width="758" height="910" alt="Image" src="https://github.com/user-attachments/assets/05d27c46-1ed7-4eec-a5af-8d213fe65600" />

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 Codex CLI burns subscription tokens when only checking /status repeatedly [3 comments, 3 participants]