| Shortcut | Action |
|---|---|
⌘N | New session |
⇧⌘N | New squad |
⇧⌘P | New project |
⌘K | Command palette |
⌘, | Settings |
⌘O | Open worktree in editor |
⇧⌘O | Open in a specific editor |
⌘D | Toggle the review panel |
⌘B | Toggle the sidebar |
⌥⌘↓ | Next session |
⌥⌘↑ | Previous session |
Why they all use Command
Fleet is a text field most of the time. A bare-letter accelerator in an app whose main control is a
composer is a trap: you would type n into a prompt and open a new session.
So every binding uses Command, and a shortcut only fires while you are typing if it uses Command itself.
Why session navigation uses Option
⌘↓ means "end of document" in a text field on macOS, and taking it would break the composer for
the sake of a convenience. Option is the free modifier.
The command palette
⌘K opens it. Everything with a binding appears there with its keys shown alongside, from the same
table, so a palette entry and the shortcut that runs it cannot drift apart.
The menu bar
The same verbs appear in the menu bar under File and Go, with the same accelerators.
Opening in an editor
⌘O opens the session's worktree in your default editor. If you have not chosen one, Fleet opens
the menu rather than guessing. ⇧⌘O always opens the menu.
The list shows the editors you actually have installed. In a development build that detection is
unreliable for the same PATH reason that hides gh and claude, so a packaged launch is where to
check it.