Queue typed input instead of interrupting running task

[nav-beep]

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.

[github-actions]

Found 3 possible duplicate issues:

1. Chained thought input — queue follow-up prompts while a task is in flight #41759
2. [FEATURE] VS Code Extension: Support queued message sending instead of interrupting current task #30677
3. [FEATURE] The ability to queue up messages.via asking the user for further info on user input. #34835

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically closed as a duplicate of #41759.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.