ccdeck weekly downloads statistics

<div align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="assets/brand/ccdeck-horizontal-on-dark.svg"> <img src="assets/brand/ccdeck-horizontal-on-light.svg" alt="ccdeck" width="274" height="64"> </picture>

ccdeck — a live dashboard for Claude Code and Codex

ccdeck is a free, open-source (AGPL-3.0) dashboard that runs on your machine and shows every Claude Code and OpenAI Codex CLI session, including ones started in a plain terminal: which Claude Code session needs input, each Claude Code subagent and every tool call as it runs, cost and quota left. Start it with npx ccdeck or the desktop app.

Step-by-step guides: ccdeck.dev/guides

Know which agent is waiting on you, and for how long.

ccdeck keeps them in one queue — every session stopped on a human, longest wait first. The topbar names them, and its count is one click to the oldest. That queue is Claude Code's, because the deck reads Codex from its rollout log and a rollout carries no such signal; the canvas under it is both, with every Claude Code subagent on a node of its own.

npx ccdeck

Or the desktop app, with the waiting count in your menu bar: macOS · Windows · Linux — every download

Generated sessions and invented quota and spend, drawn by the deck itself: assets/canvas-demo.mjs writes the log, node assets/capture-hero.mjs takes the shot. Click through for full size.

which Claude Code session is blocked on you · tool calls · one canvas · cost · quota · local · sessions never leave

ccdeck.dev · Guides · What you get · Quick start · How it works · What it touches · Accounts · Local network · Options · FAQ

</div>

---

Why

Four agents running, and the machine has been quiet for twenty minutes. One of them stopped to ask something and you 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 — so you find it by clicking through them, and the agent that was closest to finished is the one that has been waiting longest.

ccdeck answers that in one place: every session stopped on a human is at the top of the sidebar with the wait beside it, longest first, and the topbar names them beside a count that goes straight to the oldest one. The question stops being which tab and becomes this one.

That is the sharp end of a wider problem. 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 you actually have — what is running right now, what did that subagent do, which one is stuck, what is this costing — are the ones the scroll answers worst.

ccdeck draws the tree instead. It is local and needs no configuration: it registers a hook, listens, and paints.

What you get

One canvas. No tabs. No kanban.

The deck opens on these eight pictures the first time it runs — they are the whole tour, and Take the tour on an empty canvas brings them back.…