# One dashboard for every Claude Code and Codex session — installing and configuring ccdeck > Source: > Published: 2026-10-07 04:03:53+00:00 I build [ccdeck](https://github.com/BarganConstantin/ccdeck). Every step below is also on [ccdeck.dev/guides](https://ccdeck.dev/guides/), checked against ccdeck 3.38.0. Four agents running, and the machine has been quiet for twenty minutes. One of them stopped to ask something and I did not see it go by. From the outside every terminal tab looks the same — the one that is working and the one that has been holding a permission prompt since the coffee. An agent session is a tree, but a terminal shows it as a scroll. Five subagents working in parallel arrive as one interleaved column of text, and the questions I actually have — *what is running right now, which one is stuck, what is this costing* — are the ones the scroll answers worst. ccdeck draws the tree instead: one local page with every Claude Code and Codex session on the machine, sessions waiting on you at the top, every subagent and tool call live, and cost and quota beside them. This post is the install-and-configure walkthrough. `api.ccdeck.dev`: install and update events, one "active" a day, and errors, with your IP address and a device fingerprint. Your sessions, prompts, files, project names and paths are never sent. One switch under `AGENTS_DECK_NO_REPORTS=1` keeps them off from the very first start. The README's ``` npx ccdeck ``` The deck opens in your browser and gives you the prompt back. The start-up report tells you what it found: `Claude hooks`` Codex sessions``watching` when the deck found Codex, `skipped` when it did not.`server ready`` http://127.0.0.1:4317`, unless something else holds that port, in which case it takes one between 4318 and 4400 and prints it. That line is the one to trust. Running `npx ccdeck` again does not start a second deck: it prints `deck already running` and opens that deck's tab. The first time a browser opens the deck, an eight-picture tour opens by itself. `Enter` moves on, `Esc` closes it; to see it again, press `?` and click **Take the tour**. **For Claude Code**, the deck adds one hook entry per event — ten of them — to `~/.claude/settings.json` (or `$CLAUDE_CONFIG_DIR/settings.json`), running a small `hook.js` that POSTs each event to the deck on `127.0.0.1`. Your own hooks and settings stay as they are. The hook **only reports**. Claude Code's hook protocol gives a hook two ways to allow, deny or rewrite a tool call — its exit code and its stdout — and this one always exits `0` and writes nothing, so it has no way to answer at all. If no deck is running, the hook exits and your session is not slowed down. **For Codex**, nothing is installed. The deck tails the rollout files Codex already writes under `~/.codex/sessions`. Until something arrives, the canvas reads *Waiting for Claude Code or Codex*. Run `claude` or `codex` in any folder and give it something to do: *Demo data. The pill reads LIVE while it works, DONE once it stops.* A session that was already running when the deck started shows up the next time it does something. Closing the terminal **does not** stop the deck; it runs in the background. ``` npx ccdeck --status # what is running, on which port, watching which folder npx ccdeck --logs # the last lines a backgrounded deck wrote npx ccdeck --stop # the off switch ``` A deck started with `npx` does not come back after a reboot. To have it start at login: ``` npx ccdeck --install ``` That installs ccdeck globally with npm and adds a login item — a launchd agent on macOS, a `systemd --user` unit on Linux, a Task Scheduler logon task on Windows. From then on `ccdeck` works without `npx`. On Linux, systemd ends user services at logout unless lingering is on; `--install` prints the `loginctl enable-linger` command rather than running it for you. Full guide: [Install ccdeck with npx and see your first session](https://ccdeck.dev/guides/first-run/). Same deck, no Node.js, plus an icon in the menu bar (tray on Windows and Linux) that fills in when a session is waiting on you. | System | File | |---|---| | macOS, Apple silicon | [ccdeck-mac-arm64.dmg](https://github.com/BarganConstantin/ccdeck/releases/latest/download/ccdeck-mac-arm64.dmg) | | macOS, Intel | [ccdeck-mac-x64.dmg](https://github.com/BarganConstantin/ccdeck/releases/latest/download/ccdeck-mac-x64.dmg) | | Windows, x64 | [ccdeck-win-x64.exe](https://github.com/BarganConstantin/ccdeck/releases/latest/download/ccdeck-win-x64.exe) | | Debian / Ubuntu | [ccdeck-linux-amd64.deb](https://github.com/BarganConstantin/ccdeck/releases/latest/download/ccdeck-linux-amd64.deb) | | Any other Linux | [ccdeck-linux-x86_64.AppImage](https://github.com/BarganConstantin/ccdeck/releases/latest/download/ccdeck-linux-x86_64.AppImage) | The first launch has one quirk per system, because the builds are not notarised or code-signed yet: `curl -fsSL https://ccdeck.dev/install.sh | sh`, which checks ccdeck's signature and skips that prompt.` chmod +x ccdeck-linux-x86_64.AppImage`. On GNOME you also need the AppIndicator extension for the tray icon. Two things worth switching on: The app updates itself from GitHub releases, and installs a download only if it matches its checksum and carries ccdeck's own signatures. Full guide: [Install the ccdeck app on Mac, Windows or Linux](https://ccdeck.dev/guides/desktop-app/). There is no config file. Everything is a flag, an environment variable, or a switch in the page. ``` cd ~/code/my-api && npx ccdeck --scope # this folder and below only npx ccdeck --workspace ~/code/my-api # same, from anywhere npx ccdeck # every folder again ``` Guide: [Show one project's sessions](https://ccdeck.dev/guides/one-project/). ``` npx ccdeck --no-codex # Claude Code only npx ccdeck --no-claude # Codex only — no hooks, no accounts panel npx ccdeck --claude # force Claude capture if the deck did not find Claude Code npx ccdeck --codex # force Codex capture if ~/.codex is somewhere unusual ``` `CODEX_HOME` points the deck at a non-default Codex folder. Guide: [Set up ccdeck for Codex CLI](https://ccdeck.dev/guides/codex/). `npx ccdeck --port 4500`, or `AGENT_DAG_PORT=4500`. `V` opens the Sound menu: a tone for *turn finished* and one for *Claude is asking*, each with its own volume. `M` mutes from anywhere. **Notifications while closed** is in the same menu. Guide: [See which session is waiting on you](https://ccdeck.dev/guides/waiting-on-you/). | Variable | What it does | |---|---| | `AGENTS_DECK_NO_REPORTS=1` | Never send usage reports | | `AGENTS_DECK_NO_LAN=1` | Keep **Local network** (account sharing between your machines, UDP 45317) off | | `AGENTS_DECK_NO_STATUS=1` | Don't read Anthropic's and OpenAI's status pages | | `AGENTS_DECK_NO_NOTIFY=1` | Never raise a desktop notification | | `AGENTS_DECK_NO_INSTALL=1` | Don't install or update claude-swap/ccusage, no update checks, no status pages, no reports | The full list is in the README's [Options](https://github.com/BarganConstantin/ccdeck#options). | Key | Opens | |---|---| | `L` | Session list — waiting sessions first | | `W` | Next session waiting on you | | `A` | Claude accounts | | `U` | Usage: cost and quota | | `S` | This machine: CPU, memory, heat | | `V` /`M` | Sound menu / mute | | `?` | Help and the tour | `npx ccdeck` again: it opens the running deck's tab, or starts one.`npx ccdeck --claude`.`~/.claude/settings.json` is not valid JSON. Repair it or move it aside, then start again.`ccdeck: command not found`` npx` is not on your PATH. Put `npx ccdeck --install`. Guide: [Troubleshoot ccdeck](https://ccdeck.dev/guides/troubleshooting/). ``` npx ccdeck@latest --uninstall --purge ``` That removes ccdeck's hook entries from `~/.claude/settings.json`, removes its login item, stops every running deck and deletes its Local network private key. The app and the tools it installed for you (claude-swap, ccusage) are removed separately. Guide: [Uninstall ccdeck](https://ccdeck.dev/guides/uninstall/). Next in this series: sharing your Claude Code accounts between your machines, and letting them repair each other's expired logins.