IDE Extension incorrectly reports "usage limit reached" on the first request after quota reset

Resolved 💬 1 comment Opened Jul 12, 2026 by TrungH2 Closed Jul 12, 2026

What version of the IDE extension are you using?

OpenAI Codex v0.14.4

What subscription do you have?

ChatGPT Plus

Which IDE are you using?

VS Code

What platform is your computer?

Windows 10 x64

What issue are you seeing?

Summary

The Codex IDE Extension incorrectly reports that I have reached the usage limit even though my quota had just been reset.

This happened on the very first request after the quota reset.

The request starts normally and enters the "Thinking" state. Background tasks begin running, but no response is ever generated. After waiting, the extension suddenly reports "You have reached the usage limit" and the entire request is discarded.

Expected behavior

The first request after a fresh quota reset should complete successfully.

If there is not enough quota available, the extension should reject the request immediately before starting inference.

Actual behavior

  • Fresh quota after reset.
  • First prompt submitted.
  • Codex starts thinking.
  • No output is streamed.
  • Request is aborted.
  • "You have reached the usage limit" appears.
  • The prompt is lost.

This has happened more than once.

What steps can reproduce the bug?

  1. Wait until the daily quota resets.
  2. Open the Codex IDE Extension.
  3. Send the first prompt after the reset.
  4. Codex enters the "Thinking" state.
  5. Wait.
  6. Instead of producing a response, it reports "You have reached the usage limit".

Expected:
The request completes normally.

Actual:
The request is aborted with a usage limit error despite being the first request after the quota reset.

What is the expected behavior?

The first request after a quota reset should complete successfully.

If there is not enough quota available, the IDE extension should reject the request immediately before starting inference instead of accepting the request, entering the "Thinking" state, and failing later with a "usage limit reached" error.

The request should not be discarded after processing has already started.

Additional information

This issue has happened multiple times.

The quota had just been reset, and this was the first request after the reset.

The request entered the "Thinking" state and background tasks started running, but no response was generated before the extension suddenly displayed "You have reached the usage limit."

The prompt was lost completely.

I have attached screenshots showing the extension entering the "Thinking" state before the usage limit error appears.

<img width="680" height="309" alt="Image" src="https://github.com/user-attachments/assets/42ddafe1-4747-4882-abc1-d8e9ae701d2f" />

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗