AskUserQuestion popup blocks the user from reading the preceding explanation

Summary

The AskUserQuestion tool renders a blocking popup that covers the conversation, which prevents the user from reading the assistant's explanation that precedes the choice. This produces a recurring bad UX: the user is forced to pick between options before they can read the reasoning behind them.

Steps to reproduce

1. Assistant writes an explanation of the trade-offs in chat.
2. Assistant immediately calls AskUserQuestion to ask the user to choose.
3. The popup appears on top of the conversation and takes focus.

What happens

• The popup obscures the just-written explanation, so the user cannot read it before deciding.
• Frustrated users dismiss/disapprove the popup. In some cases a frustration reply (e.g. typing "errrr") gets interpreted as proceeding, so an action is taken the user did not actually approve.

Expected

One or more of:

• An option for the assistant/model to present choices inline as plain text ("Option A / Option B / Other") and accept a typed reply, instead of a modal popup.
• Make the choice UI non-blocking / dismissible so the preceding explanation stays readable while choosing.
• Keep the assistant's explanatory text visible alongside the options.

Impact

Users who rely on reading the assistant's reasoning before choosing find the popup actively hostile to that workflow. The only current workaround is to instruct the assistant to never use AskUserQuestion and to format options as text — which users should not have to enforce themselves (and which the model forgets across sessions without a hook).

Environment

• Claude Code (VS Code extension), Windows 11.