Linux Codex App: Usage quota drops by ~50% immediately after reset without any activity

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

ChatGPT Powered by Codex & OWL Version 26.803.81509 Released Aug 11, 2026

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Linux 6.17.0-35-generic x86_64 x86_64

What issue are you seeing?

Immediately after my Codex usage quota reset, my available usage dropped by approximately 50% without any activity from my side.

The quota had just reset and I had not used Codex at all after the reset.

I did not:

Send any prompts
Start a new conversation
Continue an existing conversation
Modify any code
Run an agent or task
Use Codex CLI
Use the Codex App chat
Intentionally trigger any background operation

Despite zero usage from my side, approximately half of the newly reset quota disappeared.

This appears to be a serious usage metering/accounting bug because a very large amount of quota was consumed without any user-triggered activity.

There were also no visible running tasks, prompts, or operations that could explain the usage.

What steps can reproduce the bug?

Wait for the Codex usage quota to reset.
Confirm that the quota has been refreshed.
Open or leave the Codex Linux App running.
Do not send any prompts.
Do not start or resume any conversations.
Do not run any agents or tasks.
Do not modify any files or code.
Do not use Codex CLI.
Check the usage indicator again.
Actual behavior

Approximately 50% of the quota was consumed after the reset despite zero intentional activity.

Activity after the reset

Prompts sent:

0

Code changes:

0

New conversations:

0

Existing conversations continued:

0

Codex CLI usage:

0

Intentional tasks or agents started:

0
Session information

There was no session intentionally being used when the unexpected quota consumption happened.

If there were any server-side, stale, background, or automatically resumed sessions associated with my account during this period, those may be relevant to the investigation.

What is the expected behavior?

After the usage quota resets, the available quota should remain at the newly reset amount until I actually perform an action that consumes Codex resources.

If I do not send prompts, run tasks, use Codex CLI, modify code, or interact with Codex, the quota should not decrease.

Simply having the Codex Linux App open or idle should not consume approximately 50% of the usage allowance.

If background operations are expected to consume quota, they should:
#
Be clearly visible to the user
Be associated with a specific session or task
Show what operation is consuming usage
Not consume a significant percentage of the quota without user interaction

Additional information

The most concerning part is that this happened immediately after a fresh quota reset.

The quota was newly refreshed, and approximately half of it disappeared before I had sent even a single prompt.

This may indicate an issue with usage accounting rather than normal Codex usage.

Possible areas worth investigating include:

Previous-period usage being incorrectly deducted from the new quota period
Delayed usage events being processed after the reset
Usage being double-counted
A stale or previous session continuing to consume quota
Background operations being incorrectly attributed to my account
The Linux Codex App triggering hidden usage while idle
Usage reporting in the app being out of sync with server-side quota
A reset/accounting race condition
Incorrect synchronization between Codex App usage and ChatGPT account usage

It would be useful to inspect the server-side usage logs around the exact quota reset time and identify which sessions or requests were responsible for the unexpected consumption.

I can also provide screenshots showing the quota shortly after the reset and the unexplained ~50% decrease if needed.

This is particularly serious because it can consume a substantial portion of a user's weekly allowance without any visible or intentional activity.