Codex quota was exhausted again during a short working session.

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

Version 26.611.61753

What subscription do you have?

PRO x5

What platform is your computer?

MacOS

What issue are you seeing?

Additional update: Codex quota was exhausted again during a short working session.

I am adding another observation from the same Codex session.

Session ID:
019e4f6c-c66b-7072-8678-f4370b9c5b86

Timeline:

14:14
Context: 179,518 / 258K
5-hour quota remaining: 80%
7-day quota remaining: 80%

14:19
Context: 186,991 / 258K
5-hour quota remaining: 74%
7-day quota remaining: 80%

15:06
Context: 93,534 / 258K
5-hour quota remaining: 35%
7-day quota remaining: 74%

15:20
Context: 93,534 / 258K
5-hour quota remaining: 25%
7-day quota remaining: 72%

15:43
Context: 143,431 / 258K
5-hour quota remaining: 6%
7-day quota remaining: 69%

15:58
Context: 143,431 / 258K
5-hour quota remaining: 0%
7-day quota remaining: 68%

Codex then became unavailable with the message that the Codex message limit was exhausted.

This means that within approximately 1 hour 44 minutes, the 5-hour quota dropped from 80% to 0%, and the 7-day quota dropped from 80% to 68%.

This happened during a limited number of user actions. The consumption still appears disproportionate and not transparent.

Important observation:

Between 15:43 and 15:58, the context size remained unchanged at 143,431 / 258K, but the 5-hour quota still dropped from 6% to 0%.

I also monitored local macOS process activity during the period. The system showed load, but the visible terminal output did not clearly attribute this load to Codex or ChatGPT specifically. This makes it impossible for me to verify whether the quota depletion was caused by an actual Codex task, background activity, delayed accounting, or a quota tracking issue.

Please investigate this session and provide a detailed usage breakdown showing:

• exact charged operations;
• timestamps;
• source/client;
• task or session ID;
• whether quota was consumed by user prompts, background execution, retries, indexing, tool calls, or delayed reconciliation;
• why quota continued decreasing even when context size did not change.

This is now the second time today that Codex became blocked due to 5-hour quota exhaustion under unclear circumstances.

As a paying user relying on Codex for professional work, I need transparent and auditable quota accounting.

<img width="1072" height="1192" alt="Image" src="https://github.com/user-attachments/assets/06b045e0-7264-4003-aaff-5a9ea9859fff" />
<img width="1072" height="1192" alt="Image" src="https://github.com/user-attachments/assets/91869761-0a16-4938-84cd-eee76f220fac" />
<img width="1072" height="1192" alt="Image" src="https://github.com/user-attachments/assets/26ccaec4-3c1d-4aed-8c7d-a7da49735ddd" />
<img width="1072" height="1192" alt="Image" src="https://github.com/user-attachments/assets/9a5aa1bd-e85e-41bc-bf5d-8300c174fdf9" />
<img width="1028" height="1148" alt="Image" src="https://github.com/user-attachments/assets/c52df73f-9e73-4e13-8f81-8f73552e623f" />
<img width="1072" height="1192" alt="Image" src="https://github.com/user-attachments/assets/4e8b0268-4725-4d14-b6a1-c70d17943c4b" />

What steps can reproduce the bug?

1. Open Codex in the ChatGPT macOS application.
2. Start a normal Codex work session.
3. Perform a small number of ordinary tasks involving file analysis and modifications.
4. Observe the quota indicators in the session status panel.
5. Continue working while periodically recording:

• 5-hour quota remaining;
• 7-day quota remaining;
• session ID;
• context size.

1. Observe that the 5-hour quota decreases significantly faster than expected relative to the visible amount of work performed.
2. Continue until the 5-hour quota reaches zero and Codex becomes unavailable.

Observed example from my session:

Session ID:
019e4f6c-c66b-7072-8678-f4370b9c5b86

14:14
5-hour quota: 80%
7-day quota: 80%

15:58
5-hour quota: 0%
7-day quota: 68%

Codex access was blocked due to exhaustion of the 5-hour limit.

Additional observation:

During part of the session, the context size remained unchanged while the available quota continued decreasing.

I cannot provide a deterministic reproduction sequence because the issue appears related to quota accounting rather than a specific user action. However, the behavior has now occurred multiple times during normal usage.

What is the expected behavior?

_No response_

Additional information

_No response_