Codex blocked with “workspace is out of credits” despite remaining 5h/7d usage limits in VS Code and Codex Desktop

Open 💬 5 comments Opened Jun 11, 2026 by wadamczyk-insolutions

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

Version 26.608.12217

What subscription do you have?

Business

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

I am unable to use Codex in both the VS Code plugin and Codex Desktop app with the message:

Your workspace is out of credits. Ask your workspace owner to refill in order to continue.

However, the usage/status panel still shows remaining quota:

<img width="919" height="251" alt="Image" src="https://github.com/user-attachments/assets/781ad221-ae53-4fe4-9868-d0e6ecef1814" />

<img width="282" height="227" alt="Image" src="https://github.com/user-attachments/assets/3b84ead4-0131-4699-b38b-60b9d529ee31" />

  • Same behavior occurs in:
  • VS Code Codex plugin
  • Codex Desktop app

This looks inconsistent because I still have remaining usage limits, but Codex is unavailable due to workspace credits. Why?
This blocks development work in both supported clients and creates ambiguity around whether limits or credits are the effective gating mechanism.

Please clarify whether this is expected behavior or a bug in the limit/credit display logic.

What steps can reproduce the bug?

  1. Open Codex in VS Code plugin.
  2. Start or continue a Codex session.
  3. Observe the error:

Your workspace is out of credits. Ask your workspace owner to refill in order to continue.

  1. Open Codex Desktop app.
  2. Observe the same behavior.
  3. Open status/usage panel.
  4. Observe that usage limits still show remaining quota - for example:
  • 5h limit: 10% left
  • 7d limit: 56% left

What is the expected behavior?

If the user still has remaining included Codex usage limits, Codex should remain usable until the relevant limit is exhausted.

Additional information

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗