macOS Codex Continues Consuming Weekly Limit After Task Stops at the 5-Hour Limit

Codex
1

Weekly Usage Limit Continues to Decrease After the 5-Hour Limit Is Reached and the Task Has Stopped on macOS

Hi Codex team,

I would like to report a possible usage-metering issue with the Codex macOS app.

Account and environment

  • Plan: Pro 5x
  • Platform: macOS
  • Codex was left running in the background
  • The active task had already stopped because the 5-hour usage limit was reached

Issue

After my 5-hour usage allowance was exhausted, the Codex task stopped running as expected. However, my weekly usage limit continued to decrease even though there was no active task and no visible work being performed.

Based on my previous usage, one full 5-hour usage period normally appears to consume approximately 18% of my weekly limit. In this case, my weekly usage had already decreased by around 30%, despite the task having stopped and no additional task running.

It appears that Codex may still be counting usage while the macOS app is running in the background, even after the active task has stopped due to the 5-hour limit.

Steps to reproduce

  1. Start a long-running Codex task in the macOS app.
  2. Leave Codex running in the background.
  3. Allow the 5-hour usage limit to be reached.
  4. Confirm that the task has stopped.
  5. Check the weekly usage limit afterward.
  6. Observe that the weekly limit may continue to decrease even though no task is running.

Expected behavior

Once the 5-hour limit is reached and the task has stopped, no further weekly usage should be deducted unless another task is actively running.

Actual behavior

The weekly usage percentage continues to decrease while Codex remains open in the background, even though the task has already stopped.

Impact

This makes the weekly usage calculation appear significantly higher than the actual active usage. In my case, the weekly limit decreased by approximately 30%, whereas one completed 5-hour usage period would normally account for around 18%.

Could you please investigate whether background processes, inactive sessions, or stopped tasks are still being counted toward the weekly usage limit on macOS?

I can provide additional details, screenshots, timestamps, or logs if needed.

Thank you.

2

Same issue, looks like leaving memory on is somehow consuming the weekly limit :melting_face: