Remote mobile connection does not show quota-limit state and makes agent appear silent
What version of Codex are you using?
Codex desktop app with the remote mobile connection, observed on June 13, 2026. Exact build version was not visible from the mobile surface.
What platform are you using?
- Host: macOS Codex desktop app
- Client: remote mobile connection
What issue are you seeing?
When the active Codex session reached a quota limit, the remote mobile client did not display any quota-limit message, error, or disabled-state explanation.
From the mobile client, user messages continued to appear sendable, but the agent gave no response. This made the session look broken or as though the agent was ignoring the user. The missing quota state only became apparent later outside the remote mobile experience.
Steps to reproduce
- Open an active Codex desktop thread through the remote mobile connection.
- Continue using the thread until the account/session reaches a quota limit.
- Send another message from the remote mobile client.
- Observe that no quota-limit notice is displayed and no agent response arrives.
- Send follow-up messages; the UI still does not explain why the agent is silent.
Expected behavior
The remote mobile client should immediately surface the same quota-limit state as the desktop client, including:
- a clear quota-limit message;
- whether and when usage resets, when available;
- disabling or clearly marking messages that cannot currently be processed;
- avoiding the appearance that the agent silently ignored messages.
Additional information
This is especially confusing during long-running agent tasks because silence can also look like an interrupted tool run or connectivity failure. A persistent status banner plus a failed/not-sent state on affected messages would make the failure mode clear.