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.
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
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.
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