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 above the input box 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.
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 for the turn to finish, press Ctrl+Enter. Claude Code interrupts the turn, and your queued messages go out right away, with your draft queued behind them if you had typed one. In shell mode, the key queues your command without interrupting the turn. Requires Claude Code v2.1.275 or later.
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 applies your change to the next request it makes in that turn/effort: once you confirm the cache warning, if Claude Code shows one, Claude Code applies your change to the next request it makes in that turn/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
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.
Documentation snapshot · 2026-09-23