Codex 5-hour usage limit is being consumed significantly faster since reintroduction

What version of Codex CLI is running?

OpenAI Codex (v0.149.1)

What subscription do you have?

Plus

Which model were you using?

gpt-5.6-sol medium

What platform is your computer?

WINDOWS

What terminal emulator and version are you using (if applicable)?

No response

Codex doctor report

What issue are you seeing?

Since the 5-hour Codex usage limit was reintroduced on Plus, I’m seeing a very significant increase in quota consumption compared with my previous usage of the exact same setup.

This is not just a perception caused by comparing the 5-hour limit with the weekly limit. I previously used Codex extensively with GPT-5.6 Sol while the 5-hour limit was active, and the consumption rate was clearly much lower.

With similar projects, prompts, reasoning settings and workflows, the new 5-hour allowance is now being consumed dramatically faster.

Could you please check whether there has been a change in quota accounting, compute weighting, token/tool-call weighting, or GPT-5.6 Sol consumption since the 5-hour limit was reintroduced?

I would also appreciate confirmation of whether this is expected behaviour or a potential regression.

What steps can reproduce the bug?

Uploaded thread: 01a03e46-cfd5-7f43-ab84-7b0a072380e8

What is the expected behavior?

No response

Additional information

I switched away from GPT-5.6 Sol to a lower-cost model to test whether Sol itself was responsible for the unusually fast depletion.

The 5-hour quota is still being consumed extremely quickly, including for very basic tasks such as small text/content modifications on a landing page.

This makes me suspect that the issue may not be model-specific, but could instead involve the effective size of the 5-hour allowance or its metering/accounting since the limit was reintroduced.

I had previously used Codex extensively under the old 5-hour limit, including on substantially heavier development tasks, and the practical amount of work available per 5-hour window was noticeably higher.

Additional controlled observation – GPT-5.6 Terra Medium

I now have a concrete example that suggests this is not specific to GPT-5.6 Sol.

The 5-hour allowance had just reset and showed 100% remaining before this task.

Model: GPT-5.6 Terra Medium
Task: basic landing-page content/link modifications, followed by targeted lint and production build verification.
Total working time: 6m 20s
5-hour allowance after completion: 84% remaining

In other words, this relatively basic task consumed 16% of the entire 5-hour allowance in 6 minutes and 20 seconds.

CLI output:

Worked for 6m 20s

gpt-5.6-terra medium · Context 68% left · 5h 84% left

The 5-hour meter was at 100% immediately before this request.

This reinforces my suspicion that the issue may involve the effective size or accounting of the 5-hour quota rather than GPT-5.6 Sol specifically.

No repository file, test, or entry point is named. Start by reviewing the uploaded thread and the reported quota readings, then determine whether quota metering is implemented in Codex CLI or elsewhere. Done requires identifying a reproducible accounting regression or confirming that the observed behavior is expected.