Keyboard Shortcuts

Every shortcut below appears in the app itself: click Shortcuts in the toolbar (next to Credentials and Settings), or press ? anywhere on the canvas, to open the same list. Three rows are exceptions to that. Two note a second working key combo the in-app list leaves out — Backspace for Delete, already documented in Getting Started, and Ctrl+Shift+Z for Redo, confirmed directly against InputHandler.ts. The third, Ctrl+Shift+C for Chat, is missing from the in-app list altogether, not just a second combo for an action already there — confirmed directly against toolbar.ts. Everything else here matches the in-app list exactly.

Canvas

Action	Shortcut
Search / command palette	Space or Ctrl+K
Pan canvas	Middle-drag
Zoom	Scroll
Fit to screen	Ctrl+Shift+F
Focus mode — hides the sidebar for a distraction-free canvas	F (not while editing a field)
Close panel, from an empty area of the canvas	Double-click

Selection & Editing

Action	Shortcut
Box select	Shift-drag
Select all	Ctrl+A
Duplicate	Ctrl+D
Delete	Del or Backspace
Undo	Ctrl+Z
Redo	Ctrl+Y or Ctrl+Shift+Z
Cut connector	Alt-drag across it
Disconnect a wire, by dragging away from a port dot	Drag

Workflow

Action	Shortcut
Save	Ctrl+S
New workflow	Ctrl+N
Run workflow	Ctrl+Enter
Open Chat — needs a Webhook and an Output node	Ctrl+Shift+C
Show this shortcut list	?
Navigate the workflow list	↑ ↓
Open the selected item in the list	Enter
Rename an item in the list	Double-click
Open a workflow row's menu	Right-click

Node Config

Action	Shortcut
Open a node's config panel	Double-click the node
Close the config panel	Esc
Insert node data into any field	{{

On macOS, Ctrl in the table above is Cmd; both work everywhere Aerini checks for one.

See also

• Getting Started uses several of these (Ctrl+S, Delete) as they come up naturally while you build your first workflow.
• Expressions covers what {{ inserts and how to build on it.
• Nodes Reference for what actually lives inside a node's config panel once you open it.
• Chat Panel for what Ctrl+Shift+C opens and why it's conditional on the workflow's nodes.