Account-scoped "Selected model is at capacity" on a Pro account since Sept 14 - cross-over test shows it follows the account, not the machine or network

Another Pro account with the same account-scoped "Selected model is at capacity" pattern, with a full cross-over test.

Environment

• ChatGPT Pro (headers: x-codex-plan-type: pro, x-codex-active-limit: premium), weekly allowance untouched at failure time (x-codex-secondary-used-percent: 0), 5-hour window at 63-66%.
• Codex Desktop 26.908.70816 (Windows 11) and Codex CLI 0.154.0. Also reproduced with codex exec in fresh threads with mcp_servers={}, at low / high / ultra reasoning effort.
• Models: gpt-6-astra, gpt-5.6-sol, gpt-5.6-luna, gpt-5.6-terra, gpt-5.5 all fail the same way.

Failure rate from the desktop app's own logs (local time UTC+8)

Almost all failures are Selected model is at capacity; a few are stream disconnected before completion. They return 12-60 s after the turn is submitted. Single-round turns sometimes get through; anything that needs a second sampling round dies.

Cross-over test (this is the account, not the machine or the network)

1. My account on several different computers: fails on every one of them.
2. A colleague's ChatGPT account on my computer, same office network, same Codex client: works with zero errors.
3. Other AI services on my machine work normally at the same time.

Sample failed turns (UTC)

• 2026-09-17 08:01:07Z gpt-5.6-luna thread 01a0100b-e4ec-77e2-8d52-c6d4c281833f turn 01a0ae60-5f0b-72d3-b445-91196fd9279a
• 2026-09-17 07:46:00Z gpt-6-astra same thread, turn 01a0ae54-4bcc-7601-9c81-ecd3cefb5723
• 2026-09-16 13:59:10Z gpt-6-astra thread 01a09bdb-1511-7b43-ae56-2cf8043762fd turn 01a0aa83-2499-7cb0-9a1f-a1a5fd7d368e

Server request IDs from stream disconnected before completion bodies: e6e2469e-ba60-4cd0-afc2-eb666956979a, 0ce20e89-3222-4c04-90a3-2bd0439feb52.

A support ticket was filed and escalated to a specialist on Sept 17 via help.openai.com; no reply yet. status.openai.com shows no Codex incident for any of these days.

Would appreciate an acknowledgment from the Codex team on whether this is an account-level restriction and what clears it.

The report identifies Codex Desktop 26.908.70816 and Codex CLI 0.154.0, but names no repository file, test, or entry point. Start by reviewing the account-level failure evidence and support escalation; done would require a Codex-team determination of whether the restriction is account-scoped and what clears it.