HITL prompt open: submitting a new prompt shows no feedback (indicator doesn't animate), then answers later

Summary

When a human-in-the-loop (HITL) prompt is on screen — e.g. an AskUserQuestion multiple-choice dialog or a tool-permission prompt — and the user types and submits a new prompt into the input box instead of interacting with the HITL widget, the UI appears to hang: the animated Claude indicator does not start moving, and there is no visible sign the message was received. The new prompt does, however, get processed and answered later (seemingly once the HITL state resolves or the turn advances), so the input wasn't lost — it just appeared ignored for a while.

Expected behavior

Submitting a prompt while a HITL widget is open should give immediate visible feedback that the message was accepted and is being considered (e.g. the thinking/animation indicator activates, or the message visibly enqueues), or the UI should clearly indicate the input is queued/blocked behind the open HITL prompt.

Actual behavior

• The Claude activity indicator stays static (not animating) — looks like the app is frozen or ignoring the input.
• No queued/pending affordance is shown.
• The prompt is eventually answered later, confirming it was received but with no contemporaneous feedback.

Steps to reproduce

1. In a session, trigger a HITL prompt — e.g. the assistant calls AskUserQuestion, or a tool-permission confirmation appears.
2. Instead of answering the HITL widget, type a new message in the input box and submit it.
3. Observe: no animation / no visible acknowledgement that the new prompt was received.
4. Later, observe the new prompt does get answered.

Impact

Looks like a hang/freeze. Users may re-submit, force-quit, or assume the app is broken, when in fact the input was accepted. A small feedback affordance (animate the indicator, or show "queued behind current prompt") would resolve the confusion.

Environment

• Claude Code in the Claude Desktop app
• macOS (Darwin 25.5.0)
• Model: Claude Opus 4.8

Notes

Unclear whether the new prompt should interrupt/replace the pending HITL request or queue behind it — but either way the lack of any visible acknowledgement at submit time is the core issue.