Codex Desktop consumed 80% of 5-hour usage limit within 5 minutes

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

0.130.0 版本 26.609.71450 • 发布于 2026年6月16日

What subscription do you have?

ChatGPT Plus

What platform is your computer?

windows

What issue are you seeing?

Codex Desktop consumed approximately 80% of my 5-hour usage limit within about 5 minutes of real usage.

The task I provided was explicit and limited. I did not expect a large repository-wide operation or continuous background processing. However, the 5-hour usage limit dropped very quickly, which seems inconsistent with the actual usage time and task scope.

I was using Codex Desktop on a Windows x64 machine with a large MES / Web project repository. The task was related to a specific coding request, not a request to scan or analyze the entire repository.

Please help verify whether one of the following occurred:

1. Codex Desktop scanned the entire workspace or large parts of the repository unexpectedly.
2. Background indexing or tool calls were counted against my 5-hour limit.
3. Context cache misses caused repeated large input usage.
4. The selected model or reasoning level caused unusually high usage consumption.
5. There was any abnormal usage accounting issue in Codex Desktop.

Environment:

• Plan: ChatGPT Plus
• Product: Codex Desktop
• Model: Unknown
• Reasoning level: Unknown
• OS: Windows 10 / 11 x64
• Repository size: Large MES / Web project
• Approximate files read: Unknown
• /status output: Not available
• Time started: Unknown
• Time ended: Unknown
• 5-hour remaining before: Approximately 100%
• 5-hour remaining after: Approximately 20%
• Weekly remaining before: Unknown
• Weekly remaining after: Unknown

Expected behavior:
For an explicit and limited task running for only a few minutes, Codex Desktop should not consume most of a 5-hour usage limit unless it clearly explains what operations consumed the quota.

Actual behavior:
The 5-hour limit was reduced by approximately 80% within about 5 minutes.

Impact:
This makes Codex Desktop difficult to rely on for normal development work because the usage limit can be consumed extremely quickly without a clear explanation of what consumed it.

Please clarify how the 5-hour limit is calculated in Codex Desktop and whether unexpected workspace scanning, cache misses, background indexing, or tool calls contributed to this consumption.

What steps can reproduce the bug?

I am seeing an issue where Codex Desktop shows that archived chats were deleted successfully, but the archived chats are still visible afterward.

In the Archived Chats page, I clicked the delete action. The app showed a success toast saying the archived chats were deleted. However, the chats were still listed in the archived chats view after the operation.

Steps to reproduce:

1. Open Codex Desktop.
2. Go to Archived Chats.
3. Select or delete archived chats.
4. The app shows a success message such as "Deleted 3 archived chats".
5. Check the archived chats list again.
6. The deleted chats are still visible.

Expected behavior:
When Codex Desktop shows a successful deletion message, the selected archived chats should be removed from the archived chats list and should not reappear after refresh.

Actual behavior:
The app shows a successful deletion message, but the archived chats remain visible.

Environment:

• Product: Codex Desktop
• Subscription: ChatGPT Plus
• Platform: Windows 10 / 11 x64
• App version: Unknown
• Number of archived chats affected: 3

Additional context:
This appears to be either a UI refresh issue, a backend deletion failure, or a mismatch between the success toast and the actual deletion result.

What is the expected behavior?

_No response_

Additional information

_No response_