The scarce resource is not tokens, it is my attention — why I built ccdeck

Description and use

ccdeck is a local dashboard for Claude Code and Codex agent sessions that quickly shows which agent is blocked waiting for human input and for how long, saving developer attention.

Problem

When multiple Claude Code or Codex agents run, the user cannot quickly identify which agent is blocked waiting for human input, leading to wasted attention and idle time.

Outcome

ccdeck reduces idle time by making blocked agents visible, improving developer focus and reducing wasted attention.

Workflow

• 1. Run agents via Claude Code or Codex CLI. 2. Launch ccdeck with npx ccdeck. 3. ccdeck hooks into agent events and renders a tree view. 4. The dashboard shows blocked agents at the top, sorted by wait time. 5. User switches to the corresponding terminal or agent to resolve the prompt.

Evidence

I build ccdeck, a local dashboard for Claude Code and Codex sessions.

Source

The agent was not slow. I was. And nothing in my setup could tell me that.

Source

So the first version of ccdeck did one thing: it drew the tree.

Source

say which agent is blocked on a human, and for how long.

Source

npx ccdeck

Source