ccdeck

ccdeck guides: Claude Code and Codex, step by step

ccdeck is a free, open-source local dashboard for Claude Code and Codex CLI sessions; these guides take it one task at a time, each checked against a named ccdeck release.

Get started

  1. Install ccdeck with npx and see your first session

    Run npx ccdeck with no account or API key: it opens 127.0.0.1:4317, adds a Claude Code hook, draws your first session.

  2. Install the ccdeck app on Mac, Windows or Linux

    ccdeck as an app for macOS, Windows or Linux, no Node.js: a menu bar or tray icon that gets a dot when Claude Code asks.

  3. Change ccdeck's language

    Show ccdeck's own words in one of ten languages, and go back to English or your browser's language.

  4. Set up ccdeck for Codex CLICodex only

    Start ccdeck and a Codex CLI session, read its card, watch the terminal for approvals and read your Codex quota.

Watch your sessions

  1. See Claude Code subagents and tool calls live

    Each Claude Code subagent on its own card, tool calls as they run, and any call's input and response; Codex too.

  2. See which Claude Code session is waiting for inputClaude Code only

    Claude Code sessions stopped on a permission prompt or a question, then finished turns, at the top of one list.

  3. Show one project's Claude Code and Codex sessions

    Start ccdeck with --scope or --workspace to draw only one folder's Claude Code and Codex sessions, then go back to all.

Cost and accounts

  1. See Claude Code and Codex cost and quota left

    What each Claude Code and Codex session cost at API prices, totals via ccusage, and the quota left before each reset.

  2. Switch between multiple Claude Code accountsClaude Code only

    Several Claude accounts in one panel, each one's 5-hour and 7-day quota, and a click to switch, or auto-switch.

  3. Switch between multiple Codex accountsCodex only

    Several Codex logins in one panel, each one's usage, a click to make one the default, or Auto-switch.

  4. Use your main Claude Code or Codex account first

    Auto-switch takes you to a home account and back once it has room, or uses quota that resets soonest first.

  5. Copy a Claude or Codex login to another machine

    Your Claude or Codex accounts added to a second machine's ccdeck from one pasted share, with no new sign-in.

  6. Repair Claude and Codex logins across machines

    Pair ccdeck on your machines and tick the logins to share: an expired Claude or Codex login comes back from another.

  7. Use ccdeck from a terminal or over SSH

    Claude and Codex accounts, waiting sessions and the machine in a terminal or over SSH: switch, sign in, pair decks.

Your machines

  1. See CPU, memory and heat while your agents run

    Per-core CPU, load, memory, network and temperature where there is a sensor, their history, and the busiest processes.

  2. See which tools Claude Code and Codex use most

    Count your agents' tool calls, see how long each tool takes and how often it fails, and keep or clear the history.

  3. Count the skills Claude Code and Codex use

    See which skills and slash commands your agents ran, how often, where, and whether you or the agent started them.

  4. Detect browser automation while you were away

    The pages a program opened in Chrome, Brave, Edge or Vivaldi while nobody was browsing, from each browser's own history.

  5. Change Claude Code's settings from ccdeckClaude Code only

    Change twelve of Claude Code's own settings without an editor, and look up every other one it documents.

  6. See and change Claude Code's telemetry settingsClaude Code only

    Read Claude Code's telemetry flags, switch one for new sessions, and watch plaintext traffic to your collector.

Integrations

  1. Connect Jira, read your board and move issues

    Jira Cloud or Server connected with a token, your board beside your agents, and issues commented on and moved.

  2. Connect GitHub or GitLab to ccdeck

    A read-only GitHub or GitLab token connected, and branches, merge requests and pipelines beside your agents.

Maintenance

  1. Update ccdeck to the latest version

    Update ccdeck run with npx or installed with npm, restart into the new release, and choose whether it updates itself.

  2. Uninstall ccdeck and remove its Claude Code hook

    Stop every deck, remove ccdeck's Claude Code hook, login item and private key in one command, then its app and folders.

  3. Troubleshoot ccdeck: status, logs, port and hooks

    Fix ccdeck when sessions don't appear, the port is taken or a setting won't save, starting from --status and --logs.

Short answers