While Claude Code is mid-turn and heading the wrong way, what do typing a message plus Enter, Esc, Ctrl+C and Ctrl+Enter each do?
answer
- steer, don't restart
- Enter mid-turn queues
- delivered after current tool calls
- Esc keeps work so far
- send-now backgrounds, since 2.1.281
basics
~20 sEnter mid-turn queues a message that reaches Claude after the current tool calls; Esc stops the turn but keeps work done and sends the queue; Ctrl+C interrupts, or clears then exits when idle; Ctrl+Enter sends the queue at once.
solid answer
~40 sTyping and pressing `Enter` while Claude works queues the message without interrupting; it reaches Claude as soon as the running tool calls finish, within the same turn, and `Up` takes it back for editing. `Esc` interrupts the current response or tool call so you can redirect: work done so far is kept, the queue is sent next, and an unsent draft stays unsent. `Ctrl+C` also interrupts a running operation, but at an idle prompt the first press clears your input and the second exits Claude Code. `Ctrl+Enter` (or `Ctrl+X Ctrl+S`, v2.1.275+) sends the queue now: since v2.1.281, shell commands and subagents move to the background and Claude reads your message in the same turn, and only work that cannot be backgrounded is interrupted.
go deeper
Recall that Esc stops Claude so you can redirect, and that typing while it works queues your message instead of interrupting.
Explain delivery timing: a queued message reaches Claude after the current tool calls, in the same turn; Esc sends the queue next; Ctrl+C clears then exits when idle.
Show you pick the least destructive input: queue small corrections, Esc for an imminent wrong action, Ctrl+Enter to keep a long run alive while Claude reads your note.
Frame steering as cheaper than restarting, and coach a team on which inputs preserve context and running work, including what changed in 2.1.281 for send-now.
## Why steering matters A Claude Code **turn** is everything the agent does in response to one prompt: model replies and tool calls, sometimes dozens of them. When a long turn starts heading the wrong way, restarting throws away its useful work and context. The prompt line gives you four ways to steer instead, and they differ sharply in what they keep. ## The four inputs | Input | Interrupts the turn? | What happens to your text | What happens to Claude's work | | :- | :- | :- | :- | | Type a message, press `Enter` | No | Queued, then delivered | Continues | | `Esc` | Yes | Draft not submitted; queue sent next | Kept as done so far | | `Ctrl+C` | Yes, if something is running | Idle: first press clears input | Kept as done so far | | `Ctrl+Enter` / `Ctrl+X Ctrl+S` | Depends (see below) | Queue and draft sent now | Background-able work moves to the background | ### Typing while Claude works: queued messages Pressing `Enter` mid-turn does **not** interrupt. Claude Code **queues** the message and lists it in the conversation, shown in grey until Claude starts on it. - If Claude is running tool calls, the queued message is passed to Claude **as soon as those tool calls finish, within the same turn**, so a correction can land mid-run. - If the turn ends with messages still queued, they go out automatically, in the order you typed them. - Pressing `Up` from the first line of the input box **takes back** what you queued so you can edit it. - The `chat:queueSubmit` action (`Ctrl+X Enter`) submits a draft marked to wait its turn, never interrupting. ### `Esc`: stop and redirect `Esc` stops the current response or tool call **so you can redirect**. Claude **keeps the work done so far**: files already edited stay edited. If you have messages queued, Claude Code sends them right away, and a draft in the input box is not submitted. In a dialog `Esc` closes it, and on a permission prompt it declines the action. Pressing `Esc` twice is a different input: with text it clears the draft, and on an empty prompt it opens the rewind menu, which belongs to checkpointing. ### `Ctrl+C`: interrupt, clear, exit `Ctrl+C` interrupts a running operation too. Its idle behaviour is the trap: with nothing running, the **first press clears the prompt input and a second press exits** Claude Code. It is a reserved shortcut and cannot be rebound. ### `Ctrl+Enter`: send now (v2.1.275+) `Ctrl+Enter`, or `Ctrl+X Ctrl+S` in terminals that do not report extended keys (where `Ctrl+Enter` arrives as plain `Enter`), is the `chat:sendNow` action. It sends your queued messages, with the draft behind them, without waiting: 1. If Claude is 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. 2. If Claude is only writing a response, or running something that cannot be backgrounded, the turn is interrupted and your messages go next. 3. If a queued `!` shell command sits ahead of your messages, the key interrupts the turn. Before v2.1.281 the key interrupted the turn in every case, so older advice that "send now kills the running command" is out of date. ## Choosing - **A small correction** ("use the v2 client"): just type it and press `Enter`; it reaches Claude after the current tool calls. - **Claude is about to do something wrong now:** `Esc`, then say what to do instead. - **A long test run is going and you want Claude to read your note immediately:** `Ctrl+Enter`, which keeps the run alive in the background. - **To see what Claude is actually doing before you decide,** toggle the transcript viewer with `Ctrl+O` for detailed tool usage. - Reserve `Ctrl+C` for when `Esc` is not reaching the turn, and do not press it twice at an idle prompt unless you mean to quit.
- You queued three messages and now regret the second. How do you fix it before Claude reads it?Press `Up` from the first line of the input box. Claude Code removes the queued messages and puts them in the input box, one per line, ahead of any draft. Edit or delete the line, then press `Enter` to queue the result again as one entry, or clear the box to drop it.
- Your terminal sends Ctrl+Enter as a plain Enter. What happens, and what do you press instead?The key arrives as `Enter`, so your draft is simply queued instead of sent now. `Ctrl+X Ctrl+S`, the other default binding of `chat:sendNow`, works in any terminal because it does not depend on extended key reporting.
- After Esc, is the file Claude half-way through editing rolled back?No. `Esc` interrupts and Claude keeps the work done so far, so completed edits stay on disk. Undoing them is a separate action through the rewind menu, which double `Esc` on an empty prompt opens.
- Pressing Enter while Claude works cancels the turn and starts a new one.
- Esc rolls back every edit Claude made during the interrupted turn.
- A queued message always waits until the whole turn has ended.
- Pressing Ctrl+C twice at an idle prompt only clears the input.
- Ctrl+Enter always kills the command Claude is running.
- Double Esc is just a stronger interrupt than a single Esc.
Assumes Claude Code 2.1.286; the Ctrl+Enter send-now key arrived in 2.1.275 and stopped always interrupting the turn in 2.1.281.