Codex App: allow dismissing the out-of-quota/credits prompt so users can still read conversation history

What variant of Codex are you using?

Codex App (desktop, macOS)

What feature would you like to see?

When the subscription quota (5-hour/weekly) or purchased extra credits are exhausted, the Codex App shows a prompt/dialog saying the user is out of Codex messages or has hit the usage limit.

That prompt has no way to be closed/dismissed, so it keeps covering the conversation. Even though sending new messages is legitimately blocked at 0 quota, reading and scrolling existing conversation history should still be possible. Right now the only workaround is to leave the thread or restart the app, which makes reviewing history while out of quota unnecessarily disruptive.

Requested behavior:

• Give the out-of-quota / out-of-credits prompt a visible close/dismiss control.
• Dismissing it should leave the thread readable (scrolling, selecting, copying existing messages) while still blocking new model requests and keeping the quota/upgrade state discoverable, e.g. as a compact persistent banner or via the usage/status entry point.
• If the prompt must reappear, it should be re-shown only on a new send attempt or after the quota state changes, not block reading the existing conversation.
• Ideally, once dismissed, the choice should persist for the current thread at least until the quota resets or the user explicitly reopens the quota/upgrade view.

Additional information

This also relates to the existing "You're out of Codex messages" reports (e.g. #21161, #20904, #23258), which describe the same surface appearing above/over the chat. Those focus on the prompt appearing incorrectly despite available credits; this request is about the missing dismiss affordance and the reading-history use case when usage really is exhausted.

Concrete flow:

1. Use the plan's 5-hour or weekly allowance to 0%, or exhaust purchased credits.
2. Open or resume a thread.
3. The out-of-quota/upgrade prompt appears and covers the conversation.
4. There is no close/dismiss button, so the prompt keeps blocking the user from reading history.
5. Expected: the prompt can be dismissed, the thread stays readable, and send remains disabled until quota resets or credits are added.

Environment where this was observed:

• Codex App 26.908.70816 (9275), macOS 27.0.0 arm64 (Darwin 27.0.0)
• ChatGPT Pro

Reproduce the Codex App flow by exhausting the 5-hour or weekly allowance or purchased credits, then opening an existing thread. Trace the out-of-quota prompt and its send-blocking state; done means the prompt can be dismissed, conversation history remains readable, and the prompt returns only on a new send attempt or quota-state change.