Codex Usage exhausted due to background task error, the session is inactive.

What version of Codex CLI is running?

codex-cli 0.150.1

What subscription do you have?

Plus

Which model were you using?

gpt-5.6-sol

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

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

Desktop app

Codex doctor report

What issue are you seeing?

My Codex task remained active while I was not using the application.
A browser verification tool call became stuck after requesting the unsupported networkidle state. The execution record showed a wall time of 50,729.2 seconds (approximately 14.1 hours) before the stuck call was released when I returned to the task.
During this incident:

• My 5-hour Codex usage allowance was exhausted.
• My 7-day / weekly usage allowance also decreased substantially.
• I was not actively interacting with Codex during most of this period.
  I understand that Codex usage is token- and workload-based rather than purely based on elapsed time. However, because this task remained stuck abnormally for approximately 14 hours, please review the detailed usage records for this session and
  determine:

1. Whether usage continued to be attributed while the unsupported browser operation was stuck.
2. How much usage from both the 5-hour and 7-day limits was attributed to this session.
3. Whether any duplicate, retry, background, or abnormal tool usage was recorded.
4. Whether the affected 5-hour and 7-day allowances or credits can be restored.
   Error: playwright_wait_for_load_state does not support networkidle
   Recorded tool wall time: 50,729.2 seconds
   Timezone: Asia/Taipei
   Approximate incident start: September 2, 2026, afternoon

What steps can reproduce the bug?

Uploaded thread: 01a06184-ae33-7413-b6d1-7ed37566cc27

What is the expected behavior?

No response

Additional information

No response

Start with the uploaded thread 01a06184-ae33-7413-b6d1-7ed37566cc27 and the session's usage records. Compare the 50,729.2-second tool wall time with 5-hour and 7-day allowance attribution, checking for retries, duplicate usage, or background execution. Done means the accounting and any restoration decision are documented.