Keybindings
All keyboard shortcuts can be customized via~/.atomic/agent/keybindings.json. Each action can be bound to one or more keys.
The config file uses the same namespaced keybinding ids that Atomic uses internally and that extension authors use in keyHint() and injected keybindings managers.
Older configs using pre-namespaced ids such as cursorUp or expandTools are migrated automatically to the namespaced ids on startup.
After editing keybindings.json, run /reload in Atomic to apply the changes without restarting the session.
For editor completion of every action id and validation of key syntax, add "$schema": "https://raw.githubusercontent.com/bastani-inc/atomic/main/packages/coding-agent/schemas/keybindings.schema.json" to keybindings.json. Atomic ignores $schema when it loads your bindings.
Workflow widget scrolling
app.workflows.scrollUp defaults to ["alt+k", "alt+pageUp"]; app.workflows.scrollDown defaults to ["alt+j", "alt+pageDown"]. These scroll the main-chat workflow list without leaving the editor. Any other configured editor binding takes precedence, including the Vim Alt+J/K cursor bindings. Alt+Up remains available for queued messages.
For example, replace both defaults and their aliases:
[] to disable an action, then /reload. On macOS, the widget labels Alt as Option; enable Option-as-Alt/Meta in your terminal. If a shortcut produces a character or is intercepted by your terminal or multiplexer, use the Page aliases or choose another binding. Wheel scrolling over the widget is independent of these shortcuts and requires fullscreen mouse reporting.
Some differently named keys share terminal input: for example, Ctrl+H and Backspace, Ctrl+I and Tab, or Ctrl+M and Enter. Shared input stays with the editor, and ambiguous legacy shortcuts are omitted from the widget hint. A terminal sending distinct enhanced-protocol input may still use the workflow binding. For consistent behavior across terminals, choose an unambiguous binding or use the Page aliases rather than relying on that distinction.
Key Format
modifier+key where modifiers are ctrl, shift, alt, or super (combinable) and keys are:
- Letters:
a-z - Digits:
0-9 - Special:
escape,esc,enter,return,tab,space,backspace,delete,insert,clear,home,end,pageUp,pageDown,up,down,left,right - Function:
f1-f12 - Symbols:
`,-,=,[,],\,;,',,,.,/,!,@,#,$,%,^,&,*,(,),_,+,|,~,{,},:,<,>,?
ctrl+shift+x, alt+ctrl+x, ctrl+shift+alt+x, ctrl+super+x, ctrl+1, etc. super depends on terminal support.
All Actions
TUI Editor Cursor Movement
The dedicated history actions always change history entries, regardless of the cursor position in a multiline prompt. Explicit history bindings take precedence over ordinary application action handlers while the main editor is focused, so binding
tui.editor.historyPrevious to ctrl+p or tui.editor.historyNext to ctrl+n overrides those app actions without changing the same keys in selectors.
TUI Editor Deletion
TUI Input
TUI Kill Ring
TUI Clipboard and Selection
Local copy operations require a working native clipboard or platform command. On Linux, install
wl-clipboard for Wayland, xclip or xsel for X11, or the Termux:API app and termux-api package for Termux. Fullscreen selection shows a backend-specific failure message for five seconds. Atomic forwards copies through OSC 52 in SSH or Mosh sessions and uses it as a fallback on headless Linux. Set ATOMIC_CLIPBOARD_OSC52=1, or its legacy alias PI_CLIPBOARD_OSC52=1, to force forwarding after the local clipboard attempt. The terminal must support clipboard forwarding; an OSC 52 write does not confirm a successful local copy.
TUI Fullscreen Viewport
Interactive sessions use a fullscreen transcript. The wheel scrolls the region under the pointer; over the fixed editor, status, or footer it scrolls the transcript. When scrolled up, click “Jump to latest message” or usetui.altScreen.bottom to return to live output. Attached workflow chats have their own jump link; other OSC 8 links open in the default handler.
Dragging selects and copies text by default. Set fullscreenCopyOnSelect: false to highlight without copying. See Terminal setup for mouse and trackpad behavior.
Hold Alt while using the mouse wheel to scroll five times as far in fullscreen mode. This requires the terminal to forward the Alt modifier in mouse events; focused components may still consume the wheel input themselves.
Drag with the primary button to select characters, double-click for a word or path, and triple-click for a line. Changing focus or clicking elsewhere clears the selection.
While the main editor has focus, fullscreen transcript bindings take precedence. home and end stay with the editor; ctrl+home and ctrl+end jump to the transcript top and bottom. pageUp and pageDown control the transcript, while their ctrl variants control the editor.
This routing remains configurable through the ordinary action bindings. For example,
"tui.altScreen.pageUp": "ctrl+pageUp" makes pageUp control the editor and ctrl+pageUp control the transcript in fullscreen mode. Bind tui.altScreen.halfPageUp and tui.altScreen.halfPageDown for half-page steps, or tui.altScreen.lineUp and tui.altScreen.lineDown for single-line steps, while keeping the full-page bindings. Setting "tui.altScreen.pageUp": [] disables that transcript shortcut entirely. User bindings replace the defaults for that action.
A focused custom component may consume viewport keys and mouse input before the transcript. Extension authors should follow the input handling contract.
The blocking ask_user_question dialog is a bottom-pinned overlay. Opening it does not shrink the transcript viewport or change the page step. pageUp, pageDown, ctrl+home, ctrl+end, and the wheel still reach every scrollback line, including the newest ones, in the visible strip above the dialog.
These transcript actions also work while Notes is open. Notes keeps ordinary text and edit actions, including the default home and end. A key moves the transcript instead only when configured for a tui.altScreen.* action.
On short terminals, the dialog is bounded to preserve that visible strip. The active questionnaire row stays visible as you move through single-select and multi-select choices, Next, Submit, Cancel, and inline inputs. The dialog keeps its own arrow, enter, tab, space, esc, click, and selection input.
Atomic does not ship a find-in-transcript shortcut. The four
tui.altScreen.search* actions remain in the keybinding table so an existing keybindings.json still validates, but they have no default keys and do nothing.
On Windows, pressing the secondary mouse button in fullscreen pastes text from the system clipboard into the focused component.
Application
On macOS, files copied in Finder paste as their paths, one per line, instead of the file icon. In bash mode (input starting with
!), the paths are shell-quoted and separated by spaces. When app.clipboard.pasteImage finds text rather than files or an image, Atomic inserts that clipboard text into the editor instead of reporting an image-paste failure.
On macOS, native Cmd+V also pastes a clipboard image when the copy was image-only. Terminals may deliver that as an empty bracketed-paste event or (with Kitty keyboard protocol, e.g. Ghostty) as super+v. Text under Cmd+V still goes through normal terminal paste when the terminal sends a paste event. Cmd+V is not a configurable Atomic keybinding.
Inside tmux on macOS, Ctrl+V is the reliable image-paste shortcut; native Cmd+V depends on terminal forwarding. VS Code’s terminal may forward the empty bracketed-paste route through tmux, while Ghostty may not forward its Kitty super+v route through tmux. This is terminal forwarding behavior, not an Atomic defect.
When the clipboard has both text and an image, behavior depends on the terminal: empty-paste terminals may insert the text on Cmd+V, while Kitty-protocol terminals that deliver super+v go through the image path (same preference as Ctrl+V). Ctrl+V always prefers the image. Apple Terminal may send nothing for image-only paste; use Ghostty/iTerm/Kitty or Ctrl+V in that case.
Ctrl+X does not copy messages or selections. A workflow tool-detail view closes to its graph; the scoped-model selector clears its local selection; an attached workflow stage chat returns to its graph; and a workflow graph returns to main chat. Workflow surfaces recognize the physical Ctrl+X chord directly, including CSI variants. /copy always copies the last assistant message.
On OAuth sign-in screens, Ctrl+X copies the sign-in URL, including long URLs that wrap across lines. This also works in /mcp login. Customize this shortcut with app.auth.copyUrl; it does not change Ctrl+X behavior outside sign-in screens. Remote sessions use OSC 52 clipboard forwarding as described above.
A held paused queue by itself is idle for Ctrl+C handling. After an interruption settles, the next Ctrl+C clears the editor without releasing or dequeuing the hold, and a second quick idle press exits normally.
In interactive sessions the agent runs in a supervised engine child (see Extensions). Escape there requests the engine’s cooperative cancellation and waits for it with no deadline; it never terminates or replaces the engine.
Both keys are recognized by their physical identity, not by the configured app.clear action, so rebinding app.clear cannot make Escape stop the engine or take the host route away from Ctrl+C.
Ctrl+C is the host’s escape hatch whenever an engine-owned ctx.ui.custom() component or overlay holds input: those forward every key to the engine, so a component that never resolves would swallow Ctrl+C. Which component gets the press is decided per mount, in this order:
- If the engine is provably not answering, the first press terminates and replaces it — a wedged child cannot run the component’s own handler either. “Not answering” means the watchdog has declared it unresponsive, a cooperative abort has gone unanswered past the same one-second threshold, a replacement has been waiting for readiness past it, or a replacement failed. A failed replacement keeps Ctrl+C armed so another press can try again; Atomic never retries on its own.
- Otherwise, if the component declared
handlesCtrlCwhen it was mounted, it receives the press and keeps its own Skip, Close, or cancel behavior. The bundled workflow surfaces declare it. If the same component is still holding input on the next press, that press closes it. - Otherwise the first press closes that one component, exactly as if it had been cancelled: its
ctx.ui.custom()promise resolves withundefined, the editor comes back, and the engine — along with everything else it has mounted or is running — is left alone.
tui.select.cancel still keeps Ctrl+C as local cancel inside host-native selectors, dialogs, input forms, and session pickers.
Sessions
Models and Thinking
Interactive model and thinking choices automatically become startup defaults. There is no save-default shortcut.
Display and Message Queue
Task inspector actions
These actions apply only while inspecting tasks. They do not replace global Ctrl+O, F2, or editor input. Open the inspector with/tasks.
Mounted human-input prompts and the composer retain priority. Escape leaves stdin
or task detail before leaving task focus. Unbound actions have no key hint.
Tree Navigation
Scoped Models Selector
Used inside the scoped models selector (opened via/scoped-models). Changes are saved automatically.
Custom Configuration
Create~/.atomic/agent/keybindings.json:
app.suspend opens an interactive PowerShell subshell with alt+z, leaving ctrl+z available for editor undo. Type exit to return to the same Atomic session. Atomic and its owned background tasks continue running; this is not process suspension. Ctrl+C in the subshell does not clear or exit Atomic. PowerShell 7 (pwsh.exe) is preferred, with Windows PowerShell (powershell.exe) as fallback; see Windows for the locations checked. In WSL, the normal Linux ctrl+z/fg behavior still applies.