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)?
26.623.101652
What subscription do you have?
Plus
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
Even once I open the Codex app, and do not axchange any messages nor run automation my starting usage remaining is 99%. Even asking codex in a fresh chat why is that, on GPT 5.5 Medium drained the use further making it 98% now. Never experienced something liek that beofre.
What is going on?
What steps can reproduce the bug?
Feedback ID: 019f31cf-d270-76e1-9706-a9df1b884860
What is the expected behavior?
Usage to be tied to acctual work Codex is doing and not getting drained while it is idle.
If the second one returns non-zero counts, the Chronicle research preview (screen capture → local OCR → periodic model summaries) has been running. On my Mac that path produced 6,002 background model calls in 8 days while Settings → Usage showed nothing, and asking Codex itself to investigate consumed more quota without finding it. Details and a script are in #42282.
If both come back empty, it is something else — ambient/home suggestions are another documented background caller (#29380), and delayed accounting is a third possibility.
Activity
github-actions commentedon Jul 5, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
hankwangtw commentedon Sep 2, 2026
In case it is the same cause as mine — two read-only checks that take a few seconds:
If the second one returns non-zero counts, the Chronicle research preview (screen capture → local OCR → periodic model summaries) has been running. On my Mac that path produced 6,002 background model calls in 8 days while Settings → Usage showed nothing, and asking Codex itself to investigate consumed more quota without finding it. Details and a script are in #42282.
If both come back empty, it is something else — ambient/home suggestions are another documented background caller (#29380), and delayed accounting is a third possibility.