Codex Remote/mobile reports quota exceeded while direct CLI works on same machines

Summary

Codex Remote incorrectly reports Quota exceeded. Check your plan and billing details. across desktop and mobile remote sessions, even though Codex CLI works when run directly over SSH on the target machines.

Environment

• Product: Codex Remote / Codex mobile remote session
• Date observed: May 21, 2026
• Error: Quota exceeded. Check your plan and billing details.

Machine where direct CLI works

codex --version && which codex && hostname && date
codex-cli 0.130.0
/usr/local/bin/codex
Ultron
Thu May 21 19:20:41 EDT 2026

Affected machine where Remote shows quota issue

codex --version && which codex && hostname && date
codex-cli 0.130.0
/opt/homebrew/bin/codex
cerebro.local
Thu May 21 19:21:15 EDT 2026

Steps to reproduce

1. Use Codex Remote to connect to an affected machine, for example cerebro.local.
2. Start or continue a Codex Remote session.
3. Send a prompt such as Any updates?.
4. Observe the quota error.
5. SSH into the same target machine manually.
6. Run Codex CLI directly.
7. Observe that Codex CLI itself is installed and available, and direct CLI usage works.

Expected result

Codex Remote should continue the remote session normally, or use the same valid entitlement/account path as direct Codex CLI usage. If Remote intentionally uses a different identity/account/project/quota bucket, the UI should clearly show which one.

Actual result

Codex Remote fails with:

Quota exceeded. Check your plan and billing details.

The same failure also appears in the mobile Codex UI while viewing a remote conversation.

Evidence

Desktop screenshot captured locally:

• Screenshot 2026-05-21 at 7.18.20 PM.png

Mobile screenshot captured locally:

• IMG_3392.PNG

Screenshot-visible details include:

• User prompts: Any updates?, repeated
• Error: Quota exceeded. Check your plan and billing details.
• Mobile context shown under title: .openclaw · ultron
• Mobile model/control visible: 5.5 Medium

Impact

Codex Remote is unusable for affected machines despite Codex CLI being installed and functional locally. The quota message appears misleading because this seems specific to the Remote/mobile session path rather than actual account quota exhaustion.

Suspected area

Codex Remote/mobile may be using a different identity, billing project, organization, entitlement, or quota bucket than direct CLI execution on the target machine. It may also be session-specific, since the error appears while continuing an existing remote conversation.