[Codex App] Pending user-choice dialog disappears when usage limit is reached

What issue are you seeing?

Codex reached the usage limit at exactly the same moment it presented an interactive question that required my decision.

The agent had been working for 23m 22s and had edited 9 files. It then finished installing/configuring OmniRoute and asked me to choose how model credentials should be configured.

The user-choice interface appeared, but immediately disappeared when my Codex usage reached 0%.

The task was then replaced by the usage-limit message:

"You've hit your usage limit."

As a result, I was unable to answer a question that Codex itself explicitly required before continuing.

This is especially problematic because the pending question involved credentials/API configuration, where Codex should not silently assume a choice.

Steps to reproduce

1. Start a sufficiently long-running Codex task.
2. Let the task approach the account usage limit.
3. Have Codex reach a point where it needs an interactive user decision before continuing.
4. Allow the usage limit to be reached while that user-choice prompt/dialog is displayed.
5. Observe that the interactive choice disappears and the task is stopped.

What happened?

The pending user interaction was lost as soon as the usage limit was reached.

There was no persistent "waiting for user input" state and no way to answer the question after the task had been interrupted.

What did you expect to happen?

When Codex is waiting for required user input, reaching the usage limit should not discard that interaction.

At minimum, Codex should:

• Preserve the pending question and its available choices.
• Mark the task as paused due to usage limit.
• Prevent the agent from making the pending decision automatically.
• Restore the same pending interaction after usage becomes available again.

Ideally, after a usage reset there should be a Resume task action that continues from the exact paused state instead of requiring the user to manually reconstruct the context.

Expected flow:

Codex working
→ requires user decision
→ usage limit reached
→ task becomes PAUSED
→ pending decision remains saved
→ usage resets
→ Resume
→ the same question is presented again
→ user chooses
→ Codex continues

Why this matters

Long-running Codex agent tasks can run for a significant amount of time and perform many edits before requesting user input.

Losing the execution state at the usage boundary can cause:

• loss of an important approval/decision;
• duplicated work after resuming;
• additional usage spent reconstructing context;
• incorrect assumptions by the agent;
• riskier behavior when the pending interaction concerns credentials, permissions, destructive operations, architecture decisions, etc.

A usage limit should pause execution, not invalidate an unresolved human-in-the-loop interaction.

Environment

• Platform: Windows
• Codex App
• Subscription: ChatGPT Plus
• Model: GPT-6 Astra, High reasoning
• Task duration before interruption: 23m 22s
• Files modified during task: 9
• Usage reset shown by the UI: Sep 11, 2026 at 03:12

Additional information

I have a screenshot showing the exact state:

1. Codex states that OmniRoute installation has completed.
2. Codex asks which credential configuration I prefer.
3. Directly below that question, the UI says the usage limit has been reached.
4. The interactive selection that had just appeared is no longer available.

This appears related to session/resume behavior around usage limits, but the specific bug here is that an already-open human-in-the-loop interaction is discarded when the limit is reached.

Related issues:

• #34188 — Suspend and auto-resume at usage-limit reset instead of stopping the session
• #37534 — Existing task becomes systemError and cannot resume after usage-limit response

Start by tracing the Codex App task/session state and usage-limit handling described in the issue, focusing on how pending user-choice dialogs are stored and restored. Reproduce the Windows flow with an interactive prompt near the usage boundary and verify that the pending choice survives pausing, remains unavailable for automatic selection, and can be resumed after the limit resets.