Guides
Short, step-by-step guides to ccdeck. Each one names the release it was checked against, says when a step is Claude Code only, and shows the real interface on demo data.
-
Start ccdeck for the first time
ccdeck running in the background, its Claude Code hook in place, a first session on the canvas, and the commands to check, stop and keep it.
-
Read a session on the canvas
What each card, line and bubble on the canvas means, how to open one agent's details and tool calls, and what a restart brings back.
-
See which session is waiting on you
The Claude Code sessions stopped on you, at the top of the session list with how long each has waited, and a tone when a new one asks.
-
Use several Claude accounts
Your Claude accounts in one ccdeck panel, each with its 5-hour and 7-day quota, and the active one changed with one click.
-
Install the desktop app
ccdeck running as an app on macOS, Windows or Linux, its icon in the menu bar or tray, and notifications on for when its window is closed.
-
Move a Claude account to another machine
Your Claude accounts added to a second machine's ccdeck from one pasted text, with no new sign-in, and a choice about what stays on the first.
-
Let your machines repair each other's Claude logins
Two of your machines paired over Local network, the logins each may hand out ticked, and an expired login copied back from the other.
-
See what your sessions cost and how much quota is left
Each session's spend, today's and this month's totals from ccusage, and how much Claude and Codex quota is left before each window resets.
-
Use ccdeck with Codex
Codex sessions on the ccdeck canvas from their rollout logs, with tokens and quota, what the deck cannot see, and a Codex-only start.
-
Show only one project's sessions
A deck that draws only the sessions running in one folder or under it, how to see which folder that is, and the command that brings every session back.
-
See what your machine is doing while agents run
The This machine panel open beside the canvas: cores, memory, network and heat now, what each did since the deck started, and the busiest processes.
-
Find out whether something drove your browser while you were away
The pages a program opened in your Chromium browsers while nobody was browsing, each address in full, and what ccdeck does when it finds more.
-
Update ccdeck and restart it
ccdeck on its newest release, the deck restarted into it, and a choice made about whether it updates itself while you are away.
-
Remove ccdeck from a machine
No ccdeck hook left in Claude Code, nothing starting ccdeck at login, its private key deleted, and its command, app and folders gone.
-
Fix the common problems
Which deck is running and what it last wrote, and the fix for each message ccdeck prints when a session, the port or a setting goes wrong.