You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of the Codex App are you using (From “About Codex” dialog)?
0.111
What subscription do you have?
Pro
What platform is your computer?
No response
What issue are you seeing?
Probably related to all the complaints about limits, but specifically in my case I used codex 5.3 spark for 20 seconds to create a commit message and noticed my weekly usage was down to 84% from the spark limit despite not using it for anything else. I then switched to GPT-5.2 with no more spark running and watched my spark usage decrease to 78% while my normal usage doesn't move. Then things normalised after a while.
Before this I've been experiencing very high usage using 5.4 like a number of other complaints.
Seems to me there is either the wrong model being counted for usage or there is double counting of usage going on (both as the correct model and another).
What steps can reproduce the bug?
Change to 5.3-codex-spark, run a very small task, observe possibly abnormal high effect on spark limit, change to a model that hits the normal limits, use it and possibly observe spark limit being used still.
Basically from what I can tell if I use spark in one session and then use another model like 5.4 in other sessions, for a while it still counts to my spark usage.
I didn't use Spark for quite a while, tried it for simple editing job - quote all symbol/file references in .md files (~ 55K total) - and in a few seconds my weekly quota dropped from 100% to 83% (Pro 20x plan), hourly quota dropped to ~ 61%. Another task to check if there are leftovers consumed 5% more from weekly usage and 10% from hourly.
I remember that 3-4 months ago it was not depleting so quick even on more challenging jobs.
I don't have memory enabled and use Codex CLI app (codex-cli 0.153.4).
Activity
github-actions commentedon Mar 7, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Gusarich commentedon Mar 7, 2026
If you have memory feature enabled then spark usage will be draining passively because it is used
DeanStr commentedon Mar 7, 2026
No I don't have it on
DeanStr commentedon Mar 13, 2026
Further evidence of this issue in thread 019ce81d-6db5-7cc1-abec-79dbeb959ba7
DeanStr commentedon Mar 13, 2026
019ce83b-07a0-7700-b3cb-27dc894eaa9a as well
DeanStr commentedon Mar 13, 2026
Basically from what I can tell if I use spark in one session and then use another model like 5.4 in other sessions, for a while it still counts to my spark usage.
aldem commentedon Sep 7, 2026
I didn't use Spark for quite a while, tried it for simple editing job - quote all symbol/file references in
.mdfiles (~ 55K total) - and in a few seconds my weekly quota dropped from 100% to 83% (Pro 20x plan), hourly quota dropped to ~ 61%. Another task to check if there are leftovers consumed 5% more from weekly usage and 10% from hourly.I remember that 3-4 months ago it was not depleting so quick even on more challenging jobs.
I don't have memory enabled and use Codex CLI app (codex-cli 0.153.4).