[Bug] Queued messages are incorrectly interpreted as answers to questions the user hasn't seen yet

Bug Description
_Queued messages are incorrectly interpreted as answers to questions the user hasn't seen yet_

When a step takes a while (10s+), I'll often queue my next message while Claude is still working. If Claude's response ends with a question (e.g. "Shall I commit the changes to main?"), it immediately interprets my queued message as the answer to that question – even though I typed it before the question was even visible to me.

Expected behavior: Queued messages should be treated as new instructions, not as responses to questions that appeared after they were typed.

Repro:
Give Claude a task that takes ~10+ seconds
While it's still running, type and send a follow-up message
Claude finishes, asks a clarifying question, and immediately consumes the queued message as the answer

This is especially risky with yes/no confirmation prompts – a queued message like "now update the tests" could be interpreted as confirming a destructive action the user never actually saw.

Environment Info

• Platform: darwin
• Terminal: WarpTerminal
• Version: 2.1.98
• Feedback ID: 1d92e989-edc1-4506-8b7d-0c323fbfded3

Errors

[]