Selected model is at capacity appears intermittently in active session

Summary

The app intermittently shows this error inside an active chat session:

Selected model is at capacity. Please try a different model.

This appears even when the same session can continue responding before and after the error, which makes it feel like an intermittent routing/capacity failure rather than a full session failure.

What happened

• User sent short messages in an existing session.
• The assistant responded normally to earlier messages.
• A later message produced the capacity error banner: Selected model is at capacity. Please try a different model.
• Sending another message afterward worked again.

Expected behavior

If the selected model is temporarily unavailable, the app should either retry gracefully, offer a clear fallback path, or preserve the pending user message so the user can continue without losing flow.

Actual behavior

A capacity error appears inline during an otherwise active session. The user has to retry manually or change model, even though the session itself remains usable.

Environment

• Surface: mobile app remote-control session
• Device shown in session: Sachins-MacBook-Pro.local
• Date observed: 2026-06-25
• Error text: Selected model is at capacity. Please try a different model.

Impact

This makes Codex feel unreliable for simple short-turn usage, especially when the rest of the session is still alive and responsive.