Keyboard and the command palette
Two entry points cover almost everything: Ctrl+Alt+T for a terminal at the Project root, and Ctrl+Alt+P for the command palette, which reaches every command in the application including the ones with no default chord.
The defaults
| Chord | Command |
|---|---|
| Ctrl+Alt+T | New terminal in the current Project |
| Ctrl+Alt+O | New terminal, custom |
| Ctrl+Alt+P | Open the command palette |
| Ctrl+Alt+S | Open Settings |
| Ctrl+Alt+N | Open the current Project's notes |
| Ctrl+Alt+J | Jump to a heading in the focused note |
| Ctrl+Alt+H | Split the focused pane right |
| Ctrl+Alt+V | Split the focused pane below |
| Ctrl+Alt+Z | Toggle focused pane zoom |
| Ctrl+Alt+D | Detach the focused pane |
| Ctrl+Alt+Right | Focus the next pane |
| Ctrl+Alt+Left | Focus the previous pane |
| Ctrl+Tab | Focus the next workspace tab |
| Ctrl+Shift+Tab | Focus the previous workspace tab |
| Ctrl+Shift+F | Find in the focused terminal |
| Ctrl+Alt+1 .. 9 | Activate the first nine Projects, in sidebar order |
| Ctrl+Alt+Space (held) | Push to talk, with no endpoint detection |
Commands with no default chord
Many commands ship unbound on purpose, because they already have a button in view and a chord for them would be a shortcut to something you can already see. They are all in the palette, and all of them are bindable. Among them: browsing history, opening the Projects registry, the global Scratchpad, the usage and quota views, the Automation dashboard, session rename and kill, broadcast input, pane stacking and tab movement, the sidebar filter, the application menu, and the pinned note outline.
Rebinding
Settings, Input, Keyboard shortcuts. A binding needs Ctrl, Alt, or Meta plus a non-modifier key; Shift alone is refused, because it shadows typing.
Overrides are stored in keybindings.json in the data directory. A binding for a command that was later renamed is migrated forward rather than dropped, so a chord you set does not silently stop working after an upgrade.
What the terminal keeps
swe-mux deliberately does not intercept the chords a shell or a TUI needs. Ctrl+C, Ctrl+D, Ctrl+R, Ctrl+L and their neighbours reach the process, which is why the application's own chords are behind Ctrl+Alt rather than bare Ctrl.
Mobile gestures
The same command registry is bindable to touch gestures in Settings, Input, Touch gestures. Three defaults are worth knowing:
| Gesture | Command |
|---|---|
| Two-finger swipe up | Open the current Project's notes |
| Two-finger swipe down | Read and select mode, which also lowers a keyboard being held up outside a terminal |
| Swipe up on the command rail | Toggle the swe-mux menu |
| Horizontal swipe on the top bar | Step through Projects, in sidebar order |
Voice reaches the same registry
Spoken commands resolve through voice aliases on the ordinary command registry rather than through a parallel list, which is what keeps a command reachable by chord, palette, gesture, and voice without four definitions of it. Voice covers what is deliberately excluded from the spoken set.