[Remote][Windows/Android][Pro] Existing thread falsely reports usage limit while a fresh thread on the same host works

What subscription do you have?

ChatGPT Pro.

What platform / workflow are you using?

• Host: Codex Desktop on Windows
• Client: ChatGPT Android app using Codex Remote
• Observed on: 2026-09-15, around 20:13 local time (UTC+8)
• The Windows host was online and Remote was connected normally
• Exact Codex Desktop / Android app build numbers are not available at the moment because I am away from the computer

What issue are you seeing?

One existing Codex Remote thread is stuck returning a usage-limit error even though my account still has Codex allowance remaining, and a fresh thread on the same account and same Remote host works normally.

The affected thread immediately returns:

You've hit your usage limit.
Visit https://chatgpt.com/codex/settings/usage to purchase more credits or try again at Sep 15th, 2026 9:25 AM.

At the same time, the Remote status UI shows:

7-day limit: 18% remaining
Resets on 2026-09-19

I had not used Codex earlier that day.

The displayed retry time was already in the past relative to the time of the failure, but the same existing thread continued to return the same usage-limit error.

Controlled comparison

I tested this from the same Android client, same ChatGPT Pro account, same Windows host, and within minutes of the failure:

1. Open the affected existing Remote thread.
2. Send a minimal prompt such as hello.
3. The turn fails immediately with the usage-limit message above.
4. Check Remote status: the 7-day limit still shows 18% remaining.
5. Create a new thread under an existing, previously trusted project on the same Windows host.
6. Send a prompt there.
7. The new thread works normally and returns a model response.

So this does not look like account-wide quota exhaustion or a general Remote connectivity failure. The failure appears to be specific to the existing thread/session state.

Additional control blocked by a separate Remote trust bug

I also tried to create a completely fresh No project Remote chat as another control. That fails before model invocation with the known project-trust error for an automatically generated directory such as:

C:\Users\<redacted>\Documents\Codex\2026-09-15\hello

The Android client asks me to open/trust that directory on the remote computer or start in Read only mode. This appears related to #39855 and #41470.

Because I am currently away from the Windows computer, I cannot complete that trust prompt locally.

Why I cannot provide /feedback from the affected thread

I am currently away from the computer and only have Remote access.

• The affected existing thread rejects every new turn immediately with the usage-limit error.
• A new projectless thread cannot start because of the separate project-trust gate described above.
• A new thread under an existing trusted project works, but that is a different thread and would not represent the affected session state.

So I currently have no reliable way to run /feedback from the affected thread itself.

Expected behavior

If the account has remaining Codex allowance, an existing thread should be able to continue normally.

If rate-limit state is cached or associated with a thread/session, it should be refreshed after the retry time passes and should not remain stuck when the same account can successfully execute a fresh thread on the same host.

If a thread has entered an unrecoverable stale state, the UI should surface a distinct session/thread error and provide a recovery path rather than reporting account quota exhaustion.

Actual behavior

The old thread remains blocked by You've hit your usage limit, while a fresh thread in an existing trusted project works normally under the same account and host.

Workaround

Creating a new thread under an already trusted project currently works.

Related issues

• #44823 — false usage-limit error in a Remote project while usage remains
• #39855 — Windows Remote projectless chats fail trust verification
• #41470 — Windows/Android Remote new thread hits project trust gate
• #23019 — usage-limit retry time / timezone presentation

I have redacted screenshots showing the false usage-limit error, the 18% weekly allowance remaining, and the projectless trust error. I can attach them once an attachment-capable path is available.

Start by tracing the Codex Remote thread/session handling and usage-limit path, then compare it with the fresh-thread path under an existing trusted project. Reproduce the old-thread failure against the working new-thread control; done means the existing thread no longer reports quota exhaustion when allowance remains, or exposes a distinct recovery error.