Documentation

How the deck works, what each part actually does, and where the edges are.

InstallmacOS today; Windows and Linux as they land. Your first workspacePoint it at a repo and get one agent doing real work. Panes and agent CLIsThe eleven CLIs it detects, and how to add your own. What walk-away doesExactly what it changes, and what still stops an agent. Routing and spendPicking a model per task, and capping what it costs. MaestroPlan-gated orchestration with cross-vendor review. Swarm and worktreesSeveral agents on the same task, each isolated. PluginsMCP servers, and which CLIs actually receive them. RoutinesScheduled work, and what schedules it cannot yet express. MemoryThe per-workspace markdown graph, on your disk. Phone remoteOff until you turn it on. What the phone can and cannot do. UpdatingHow new versions reach you, per platform. TroubleshootingThe failures we have actually seen, and their fixes.

What these docs try to be

Documentation that only describes the happy path is a support queue with extra steps. Where a feature is limited, unavailable on your OS, or does nothing at all for the CLI you happen to use, these pages say so on the page about that feature — not in a footnote.

Two examples you can check right now: walk-away does nothing for five of the eleven agent CLIs, because those CLIs ship no flag for it; and the write fence that makes walk-away safe is an OS sandbox, so on a machine that has none, it is not a boundary. Both are on their pages.

Found something wrong?

These pages are checked against the source, not written from memory, but the app moves fast. If a page and the app disagree, the app is right and we want to know — info@deckspace.dev.