Queue typed input instead of interrupting running task

Description

When Claude Code is actively processing a task, typing and submitting a new message immediately cancels the in-progress work and starts on the new instruction. This can be disruptive if you're just trying to queue up your next thought while waiting.

Requested Behavior

Instead of treating new input as an interrupt, consider:

• Queuing submitted messages so they run after the current task completes
• Or at minimum, showing a confirmation prompt ("Claude is still working. Cancel current task and start new one?")

Current Behavior

Any message submitted while processing acts as a hard interrupt - the current operation stops and the new instruction begins immediately. There's no way to queue follow-up instructions without waiting for the current task to finish.