[BUG] Cmd+Enter no longer queues message — now interrupts agent's current response

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?

In a recent version, the message queueing behavior via Cmd+Enter was changed/broken.

Previously:

• Enter — sends the message immediately, and it gets merged into the agent's current reasoning/response (i.e., injected into the ongoing turn).
• Cmd+Enter — queues the message to be sent after the agent finishes its current response.

Now:

• Cmd+Enter interrupts the agent's current response and sends the new message immediately, instead of queueing it.
• There appears to be no way to queue a follow-up message while the agent is still working.

This removes a workflow that many users relied on: queueing up multiple instructions while the agent is busy, without interrupting its current train of thought.

What Should Happen?

Cmd+Enter should queue the typed message and send it only after the agent completes its current response, without interrupting the ongoing generation — matching the previous behavior.

Error Messages/Logs

Steps to Reproduce

1. Start a task that takes the agent some time to complete (e.g., ask it to refactor a file or run a multi-step task).
2. While the agent is still working, type a new message in the input box.
3. Press Cmd+Enter.
4. Observe: the agent's current response is interrupted and the new message is sent right away, instead of being queued for after the current response finishes.

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude 1.49585.0 (41ad1d)

Platform

Other

Operating System

macOS

Terminal/Shell

Other

Additional Information

Separately (may warrant its own issue): the project filter that was previously available also appears to have been removed in a recent version, and there's an open related report that's been unaddressed for over a month.