GuidesClaude Code

6 Claude Code keys that save you retyping

By Stephen Thorn · 4 minute read ·

6 Claude Code keys that save you retyping, waiting and starting over

Each of these is one key or one short command. They get a cleared prompt back, send a correction while Claude is still working, undo a /clear, ask a side question, copy an answer cleanly, and run a second job without a second terminal.

What you need

  • Claude Code in the terminal. Some keys need a recent version, and each section says which. Check yours with claude --version, and run claude update to get the latest.

  • On a Mac, Ctrl means the Control key, not Command.

1. Up: get a cleared prompt back

When Claude's idle, Ctrl+C clears everything in the prompt box. One slip, and a long prompt is gone.

  • Press Up while the box is still empty, and the whole draft comes back, including text you pasted in and images.

  • Cleared it with Esc twice instead? Press Up. The docs: "double Esc clears it and saves the draft to history so Up recalls it."

  • Press Up before you type anything else. It works while the box is still empty.

  • Needs Claude Code v2.1.288 or later.

2. Ctrl+Enter: send it now

Anything you type while Claude's working sits in a queue, in gray, until Claude gets to it. Ctrl+Enter sends all your queued messages at once.

What happens next depends on what Claude was doing:

  • Running a shell command, a subagent 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 reply: Claude stops and reads your messages next

  • Ctrl+Enter acting like Enter? In terminals that don't report extended keys, it arrives as plain Enter and queues your message instead. Press Ctrl+X, then Ctrl+S. That pair works in any terminal.

  • Needs v2.1.275 or later. Keeping the command running in the background needs v2.1.281 or later. Before that, the key cancelled the turn.

3. Esc twice: undo a /clear

/clear starts a fresh conversation, and the old one's still saved.

  1. With the prompt box empty, press Esc twice. That opens the rewind menu. /rewind opens the same menu.

  2. If you ran /clear earlier and haven't quit Claude Code since, the top line reads /resume <session-id> (previous session).

  3. Pick it, and you're back where you were.

  • The entry is there until you quit Claude Code or resume a different session. After that, type /resume and pick the old chat.

  • If there's text in the box, Esc twice clears the text instead. Press it again on the empty box.

  • Tip: /clear my-label names the old chat, so it's easy to find in /resume.

4. /btw: ask a side question

Don't stop Claude to ask something quick. Type /btw and your question:

/btw what did I say the deadline was?

  • Claude answers from the session so far, and the question and answer never enter the main chat.

  • It works while Claude's busy, and the main job keeps running.

  • It can't open files, run commands or search. It only knows what's already in the session.

  • In the answer, press c to copy it as raw Markdown.

  • Press f to start a helper that has the whole conversation plus your side question, with full tool access, so it can do the work. The f key works in local sessions only.

  • In the VS Code extension, /btw opens a side panel instead (extension v2.1.227 or later).

5. /copy: copy an answer without the mess

Dragging your mouse over an answer copies the line breaks your terminal adds. /copy puts Claude's last answer on your clipboard as clean text.

  • If the answer has code or a quoted draft in it, you get a picker. Choose one block, or the full response. You can also choose "Always copy full response" to skip the picker next time.

  • Press w in the picker, and it writes your pick to a file instead.

  • /copy 2 copies the answer before the last one.

  • A quoted draft copies without its > markers. That needs v2.1.295 or later.

  • On iTerm2, run /terminal-setup once so /copy can reach your clipboard, then restart iTerm2.

6. Left arrow: park a session and start a second job

Don't open a second terminal.

  1. On an empty prompt, press the left arrow. Your session moves to the background and keeps working.

  2. You land in agent view, one screen for all your background sessions: what's running, what needs your input, and what's done.

  3. Type a new prompt at the bottom and press Enter to start a second job.

  4. Press Esc to go back to the first one. To open any other session, select it and press Enter or the right arrow.

  • Moving a session to the background never stops it.

  • claude agents opens agent view from your shell. claude attach <name> needs v2.1.290 or later.

  • Background sessions use your plan's usage the same as interactive ones, so 2 at once use it about twice as fast.

  • They run on your computer. Sleep is fine, but shutting down or restarting stops them.

  • Agent view is a research preview. Anthropic says "The interface and keyboard shortcuts may change as the feature evolves."

The mistake to avoid

Pressing Ctrl+C twice to clear a prompt. With nothing running, the first press clears the prompt and the second press exits Claude Code. Press it once, and if you wanted that draft after all, press Up straight away.