[BUG] Interrupt functionality not working as documented—second prompt queued instead of interrupting current task

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

According to the official Claude Code documentation (Interrupt and steer), users should be able to interrupt Claude Code at any point by typing a correction and pressing Enter. The documentation states: "Claude will stop what it's doing and adjust its approach based on your input."

Behavior Observed:
The second prompt is queued instead of interrupting the current task. Claude continues working on the first prompt and does not stop to process the new input.

Environment:

Claude Code CLI based Version:

What Should Happen?

Expected Behavior:
When a long-running prompt is in progress and a second prompt is entered, Claude should immediately stop the current task and switch to processing the new prompt.

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce:

1. Start a Claude Code CLI session
2. Enter a long-running prompt
3. While the prompt is still executing, type a second prompt and press Enter
4. Observe that the second prompt is queued rather than interrupting the current task

Claude Model

Other

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.143

Platform

Other

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_