Feature Request: Message queue mode — queue messages instead of interrupting active tasks #50246

Problem

When Claude is actively working on a task, the only option is to interrupt it. If I think of a follow-up mid-task I either have to interrupt and potentially derail the current work, or try to remember it until Claude finishes.

Proposed Solution

Add a message queue mode alongside the existing interrupt behavior:

• A toggle or modifier (e.g. Shift+Enter, or a dedicated queue button) that sends the message to a queue instead of interrupting
• Claude finishes its current task, then automatically picks up the queued message in order
• User can choose between two modes:
  • Interrupt (current behavior) — sends immediately, stops current task
  • Queue (new) — holds the message, delivered automatically when the current task completes

Why It Matters

Long-running tasks (builds, encodes, multi-step workflows) are common in Claude Code. A queue lets users capture follow-up thoughts as they happen without derailing active work. It also enables a more natural async workflow where the user stays in flow rather than waiting and watching for task completion before typing the next thing.

UX Suggestion

A small queue indicator near the input box showing pending messages would give confidence that the queued message was captured and will be acted on.