Token Usage for CLI 0.118.0 reported as "Other"

Resolved 💬 6 comments Opened Apr 2, 2026 by Saaketh0 Closed Apr 19, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

codex-cli 0.118.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.3-codex / gpt-5.4

What platform is your computer?

Darwin 24.6.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

Ghostty 1.3.1

What issue are you seeing?

In the past 3 days, all the cli usage that has happened has been labeled as other, which I've seen documented before and has been stated fixed in version 0.116, but is still showing up.

In addition, my token usage has been skyrocketing, having melted through my entire weekly usage in 1 day using one instance of codex despite having never reached the limit before operating on 2-3 instances on separate work trees.

I was wondering if these two issues were correlated, as in the previous issues many had the same issue as me. In addition, when accessing /status in CLI, my plan is listed as (Free), despite having paid for the plus.

<img width="1206" height="406" alt="Image" src="https://github.com/user-attachments/assets/f2de48d8-c281-456b-a424-6aa6794006ad" />

What steps can reproduce the bug?

Prompt CLI normally, fully a token usage issue.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

6 Comments

github-actions[bot] contributor · 3 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #16261
  • #15336
  • #15145
  • #15130
  • #16537

Powered by Codex Action

etraut-openai contributor · 3 months ago

The misreporting of "other" is not related to usage accounting.

erra0002 · 3 months ago

I’m experiencing the same issue

etraut-openai contributor · 3 months ago

A fix is in place for the "Other" reporting for the CLI. Just waiting for the next deployment.

rfahmi89 · 3 months ago

Moved to correct threat

etraut-openai contributor · 3 months ago

This change is now in place.