Download
Docs/Start here/Your first deck

Your first deck

Open an agent pane, split it, put the next repo in its own workspace — the dozen keys that carry the whole app.

Raw markdown

Open an agent

⌘N opens the agent picker. It lists the coding-agent CLIs Mandeck knows how to launch, each with a pill: Ready when the binary is on disk, Set up when Mandeck could not find it.

That pill is a hint, not a gate. Mandeck resolves it without spawning a process, by probing the directories agent installers actually use — and a Finder-launched app does not inherit your login-shell PATH. The pane itself runs a login shell with the full PATH, so a spawn can succeed on an agent the picker calls Set up.

An agent runs in its own pane, with its own session and its own working directory. ⌘O opens a project folder.

KeyDoes
⌘NNew session (agent picker)
⌘OOpen project
⌘KFind sessions
⌘B / ⌘\Toggle sidebar

Split the deck

The point of a deck is watching more than one agent at once.

KeyDoes
⌘DNew terminal pane
⌘⇧DSplit down
⌘↩Maximize / restore pane
⌘WClose pane / dock
ClickFocus pane

One workspace per project

A workspace is a tab. Give each repo its own and the deck stops being a wall of panes.

KeyDoes
⌘TNew workspace
⌘1–9Jump to workspace
⌘[ / ⌘]Previous / next workspace
Double-clickRename tab
DragReorder tabs

The rest of the window

KeyDoes
⌘PCommand palette
⌘⇧EFiles dock
⌘UWeb pane
⌘⇧SYour stats
⌘FFind in terminal
⌘⇧RReveal cwd in Finder
⌘/This shortcuts list
⌘,Settings

The full keymap is on Keyboard shortcuts, and it is fixed — the native build ships a discoverable keymap with no remapping surface.

Now hand work to a pane

Once two agents are open, one of them can drive the other. That is the Deck API: a local HTTP API on 127.0.0.1:7717 that spawns panes, reads their screens, answers their prompts, and tracks whether the work actually finished. Start at Jobs & hand-offs.