Keyboard shortcuts

Reading this page

Shortcuts are written the way the app writes them in English: Ctrl+Shift+A, Ctrl+Enter, Esc. The “Where” column says where each one works:

• “Everywhere”: anywhere in the window, as long as no dialog (settings, commit, ticket…) is open. On Windows and Linux, though, a terminal that has focus keeps some of these keys for its shell: see Terminals.
• “Everywhere, terminals included”: even when a terminal has focus.
• A specific place (the message field, the editor, a form…): the shortcut only works there.

Esc closes the open dialog. Two notes on the keyboard:

• Global shortcuts ignore any combination with Alt, because Ctrl+Alt is AltGr on a French keyboard. The shortcuts that use Alt belong to one area: Alt+1 … Alt+9 (questions), Alt+← and Alt+→ (editor), Alt+↑ and Alt+↓ (worktree settings), Alt+click (editor).
• The digits of Ctrl+1 … Ctrl+9 and Alt+1 … Alt+9 are read from the physical key: on an AZERTY keyboard, you don’t need Shift.

On macOS

Ctrl becomes ⌘, and Ctrl+Shift becomes ⇧⌘: Ctrl+N is written ⌘N, Ctrl+Shift+A is written ⇧⌘A. The exceptions:

Navigation

Palettes and lists

Agents and conversation

Questions and permissions

When Claude asks a question or requests a permission, you can handle the card from the keyboard:

These keys work in the conversation, message field included, or when nothing else has focus. They don’t work in a terminal, in the editor, or while a dialog is open. The details:

• Several requests can be waiting: the keyboard answers the first one.
• A request that has just arrived ignores these keys for half a second, Enter in the message field included: the text you have already typed stays there. So a Ctrl+Enter meant to send your message doesn’t answer a request that arrives at the same moment, and a second Ctrl+Enter doesn’t answer the next request. A key held down answers only once.
• A request that Claude Code would deny by default can only be allowed with its button.
• A single-choice question is sent as soon as you pick an option. With several questions or a multiple choice, Ctrl+Enter moves on to the next question that has no answer, then submits once all of them have one.
• In the overview, Ctrl+Enter does nothing: a permission that can be read in full there is allowed or denied with its buttons.

Editor

The built-in editor. Its shortcuts work as long as it is open.

The text

The text is a CodeMirror editor: its other usual shortcuts work there too.

The file tree

These keys apply when a row of the file tree has focus.

In the results of “Search in files”, Enter in the field runs the search, ↓ moves to the results, and ↑ from the first one goes back to the field.

Terminals

The log of a launch command is read-only: apart from copying and scrolling, all its keys go to the app, Ctrl+K and Ctrl+P included.

What stays with the shell

On Windows and Linux, a terminal that has focus keeps Ctrl plus a letter for its shell, including Ctrl+K (cut to the end of the line), Ctrl+P (previous command), Ctrl+N, and Ctrl+T: to search the conversations, open a file, or create an agent or a terminal, click outside the terminal first. The app only takes Ctrl+Tab and Ctrl+Shift+Tab, Ctrl+1 … Ctrl+9, Ctrl+J (to a shell it is only a line feed, which Enter already sends), Ctrl+,, and Ctrl+Shift+A. Ctrl+Shift plus a letter sends nothing to the shell: Ctrl+Shift+B and Ctrl+Shift+L work in a terminal too, where Ctrl+Shift+F searches its output.

On macOS, the app’s shortcuts use ⌘, which the shell never receives: they all work in a terminal, except ⌘C, ⌘V, and ⌘A (select all), which are the terminal’s own. The Ctrl keys go to the shell.

Panels and layout

A separator that has focus (with Tab) can be adjusted from the keyboard:

• The editor’s files column: ← / → narrow or widen it, Home and End go to the minimum and maximum width.
• The task list of the “Plan” banner: ↑ / ↓ change its height, Home and End go to the minimum and maximum, Enter or Esc restore the usual height.

A double click on a separator restores its size too.

Tickets

Settings