Get started
Install
One command in the terminal downloads the app, checks it and installs it. No repository, no git, no Node.
Before you install
| System | Requirement |
|---|---|
| macOS | Apple Silicon. The installer refuses other architectures. |
| Windows | Windows 10 version 1903 or newer, or Windows 11. |
| Both | A terminal agent installed and logged in, and a Deck account. |
The account is created on first use, with e-mail and password or with your Google account. What it keeps is in Account and privacy.
macOS
curl -fsSL https://storage.googleapis.com/deck-releases-maze/deck/install.sh | bashThe command downloads the current release, checks the SHA-256 sum against the published manifest and only then installs. The app lands in /Applications/Deck.app, or in your personal applications folder when the account has no administrator rights.
tmux, so sessions outlive the app
Deck works without tmux, but sessions end when the app does. With tmux installed, they become real sessions on a server that belongs to Deck: closing the window, updating the version or the app crashing does not take down what is running, and everything comes back in place on the next boot.
brew install tmuxDeck uses its own socket and its own configuration, apart from any tmux you already run. It does not read your .tmux.conf.
Windows
In PowerShell:
iwr https://storage.googleapis.com/deck-releases-maze/deck/install.ps1 -UseBasicParsing | iexThe install goes to %LOCALAPPDATA%\Deck and creates the Deck shortcut in the Start menu. The same integrity check as on macOS happens here.
There is no tmux on Windows, and what holds the sessions is a Deck service that starts with the app. With the service up, sessions survive closing and updating Deck, the same as on macOS. When it cannot start, the app says so and sessions live only while the window is open.
The diagnostics screen, under Settings, tells you which of the two modes you are in. On a machine with antivirus, the service can take a few seconds on the first boot.
Install an agent
Deck ships no agent of its own: it finds the ones already installed on your system and uses the login each one already has. If the agent list comes up empty when you create a session, nothing was found on your shell search path.
- Install the agent its official way and log in once, from the terminal.
- Confirm it answers in the terminal, with its version command for instance.
- Reopen Deck. The app re-reads the search path on startup.
The details of each agent, including what changes between them, are in Agents.
Update
When a release ships, a notice appears inside the app. One click downloads it, checks the integrity and restarts. On macOS the tmux sessions stay up through the swap. The same update command also lives in the command palette, which helps when the notice ignores your click.
Rescue on Windows
If the app is stuck on a version with a broken updater, this command swaps it for the current release without taking the sessions down:
iwr https://storage.googleapis.com/deck-releases-maze/deck/update.ps1 -UseBasicParsing | iexUninstall
- In Settings, use the option that removes what Deck added to the Claude Code configuration file.
- Quit the app. On macOS, also end the sessions running in Deck's tmux.
- Delete the application:
/Applications/Deck.appon macOS, or the folder at%LOCALAPPDATA%\Deckon Windows. - To wipe everything, delete the app data folder too, listed in Where the files live.
Deleting the app does not delete your projects or the worktrees left on disk. They are ordinary git folders.