Skip to content
← Back to release · 2.1.275
New features / v2.1.275

Send-now key for queued messages

CHANGELOG · original

Added a send-now key (ctrl+enter, or ctrl+x ctrl+s) that interrupts the current turn and sends all queued messages at once; sent and queued messages show in gray until the model receives them
Open official changelog ↗

Documentation

Documentation excerpt

Queue messages while Claude works

Type a message and press Enter while Claude is working. Claude Code queues the message instead of interrupting the turn, and lists the queued entries in the conversation until it sends them. You can queue ! shell commands and most commands the same way, apart from the commands, such as /status, that Claude Code runs as soon as you send them.

Sent and queued messages show in gray until Claude starts responding to them, so you can tell which messages Claude hasn't started on yet.

If you queue a message with a selection attached from a connected IDE, it keeps the selection you had when you pressed Enter, whatever you select afterward.

When Claude Code sends what you queued

When a queued entry reaches Claude depends on what you queued.

  • Messages: if you queue a message while Claude is running tool calls, Claude Code passes it to Claude as soon as those tool calls finish, within the same turn. When the turn ends with messages still queued, they go out without another key press, in the order you typed them
  • Commands and shell commands: Claude Code holds them until the turn ends, then runs them one at a time, keeping the order you queued them in

To send what you queued without waiting, press Ctrl+Enter. Your queued messages go out right away, with your draft queued behind them if you had typed one. Requires Claude Code v2.1.275 or later.

If you queued a ! shell command ahead of your messages, the key interrupts the turn. Otherwise, what happens to the turn depends on what Claude is doing when you press the key:

  • Running shell commands, subagents, or other work that can move to the background: that work moves to the background and keeps running, and Claude reads your messages in the same turn
  • Only writing a response, or running something that can't move to the background: Claude Code interrupts the turn and sends your messages next. Before v2.1.281, the key interrupted the turn in both cases

In shell mode, the key only queues your command. In terminals that don't report extended keys, Ctrl+Enter arrives as plain Enter and queues the draft instead; Ctrl+X Ctrl+S works in any terminal. Both keys are bindings of the chat:sendNow action.

Press Esc to interrupt the turn without submitting your draft. Claude Code keeps what you queued and sends it right away.

Claude Code runs some commands as soon as you send them instead of queueing them, among them /model, /effort, and /fast. Each of the three changes a setting: the model, the effort level, or fast mode. Whether Claude Code applies the new setting to the turn Claude is already working on, or only from your next turn, differs by command:

  • /model: once you confirm the cache warning, if Claude Code shows one, Claude Code uses the new model from the next request it makes in that turn
  • /effort: the next message you send runs at the new level. To start it in the turn Claude is already working on, queue a message while Claude is running tool calls
  • /fast: Claude Code keeps the fast mode setting that was active when the turn started, so your speed change applies from your next turn. If your current model doesn't support fast mode, turning it on also switches your model, and Claude Code uses the new model from its next request in that turn

Background a session with messages queued

When the session moves to the background after you press ←, the messages you had queued move with it. Claude reads them there in the order you sent them.

Commands and ! shell commands can't move, and neither can some messages, such as one with an IDE selection attached. If you press ← while one of them is queued, the session stays in the foreground and a notice that begins Cannot open agents appears. To background the session, get the entry out of the queue and then press ← again:

  • Commands and ! shell commands: wait for them to run at the end of the turn, or take them back and clear the input box. While anything else is queued, you can't take ! shell commands back, so wait for them to run.
  • Messages that can't move: wait until Claude has read them

Take back what you queued

Press Up from the first line of the input box to take back the queued messages and commands. Claude Code removes them from the queue and puts them in the input box, one per line, ahead of any text you had typed. Edit the text and press Enter to queue it again as one entry, or clear the input box to drop it.

Claude Code takes back queued shell commands only when the input box is empty and you have nothing else queued, and it switches the input box to shell mode when it does. Otherwise it leaves them in the queue, listed with their ! prefix, and runs them after the turn ends.

If you take back queued text while ← waits to background the session, the text stays in the input box and Claude Code cancels the switch. If you take it back at the moment the session moves, the text disappears with the foreground screen: it wasn't sent. Each message you took back is saved as its own entry in command history. To recover one, reopen the session and press Up on an empty prompt with nothing queued.

Documentation snapshot · 2026-11-20

Change details