[FEATURE]

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When I'm typing a follow-up message in the queue input during an active Claude Code session, permission or question prompts can appear in the same interaction area and interrupt that typing flow. This creates a focus conflict between composing my next message and responding to runtime prompts. I want to keep writing uninterrupted and decide on prompts after I finish my thought.

Proposed Solution

Please separate queued message composition from permission/question prompts in the interactive UI. The queued input box should remain stable and uninterrupted while I type. Any prompt such as permission approvals or AskUserQuestion-style interactions should appear in a separate, clearly distinct prompt area and wait for my response without taking over the compose flow. In effect, let me finish composing queued input first, then handle pending prompts in order.

Alternative Solutions

Current workaround is to stop typing and respond to prompts immediately, or try to retype interrupted input afterward. This is error-prone and breaks flow. Related issues indicate adjacent behavior (queueing and prompt timing/focus), but none appears to request explicit UI separation of compose vs prompt areas.

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

1. I start a long-running task in Claude Code.
2. While it runs, I begin typing my next message in the queue input (e.g., "Queue another message...").
3. A permission prompt or clarification question appears.
4. Today, this can interrupt my composition flow.
5. With the proposed change, my typed draft remains uninterrupted in the compose area, and the prompt waits in a separate prompt panel.
6. I finish my draft, submit/keep it queued, then answer pending prompts.
7. This reduces context switching and avoids losing train of thought.

Additional Context

Potentially related (not exact duplicate) issues found while scanning:

• #50246 Feature Request: Message queue mode — queue messages instead of interrupting active tasks
• #74629 Give the model provenance & timing context for user input
• #78185 AskUserQuestion popup steals focus mid-typing (VSCode)
• #78255 Queued/interrupted input consumed mid-turn as phantom instruction

Screenshots:
!Claude Code UI showing queued input box while task runs
!Permission prompt overlay appearing while composing input

Request focus: explicit UI/interaction separation between message composition and permission/question prompts.