One terminal has Claude Code working on a feature. Another has Codex investigating a failing test. You switch back to your editor, and a few minutes later you need to work out where both tasks stand.
Opening each terminal works. With several sessions, it becomes a recurring part of the job.
I build ccdeck, a free, open-source dashboard for Claude Code and Codex CLI. It gives those sessions a shared view while you keep using your existing terminals. Here is a small exercise for deciding whether that view helps your workflow.
Start with two tasks you already understand
Choose two independent tasks: investigating a test failure and reviewing a separate module, for example. Give each agent a clear stopping point, such as reporting its findings before editing files.
If both tasks will change the same repository, use separate worktrees. Claude Code documents this workflow: each session gets a separate working directory and branch. You still need to review and integrate the results.
For this exercise, leave both agents in the terminals where you normally use them.
Add the shared view
With Node.js 18 or newer installed, run:
npx ccdeck
The startup report prints the local address. It is usually http://127.0.0.1:4317; use the printed address if that port is occupied. A desktop app is also available for macOS, Windows and Linux, without a separate Node.js installation.
Before starting: ccdeck sends usage reports by default. Session prompts, replies and file contents are not included, but reports include system information, an IP address and a device fingerprint. To disable reports from the first launch, set AGENTS_DECK_NO_REPORTS=1 in the environment that starts ccdeck. The first-run guide explains the setup and what it changes.
Start a fresh Claude Code session and a fresh Codex CLI session, then give each its task. Using fresh sessions makes this exercise easier to follow than trying to reconstruct work already in progress.
Claude Code events arrive through a hook that ccdeck adds to its settings. Codex activity comes from the rollout files its CLI writes. Those are different capture paths, and they have different limits.
Use it to answer three questions
Which session should I check next?
Look at the session list before opening a terminal. Claude Code sessions waiting on you appear together, with their waiting time. That gives you a place to start when several tasks are in flight.
Codex approval requests are not visible in its rollout files. Keep its terminal available: a tool waiting for approval can look like a tool still running. The shared canvas covers both providers; the waiting queue is Claude Code only.
What happened inside that task?
Double-click a node to inspect the captured prompt, tool calls, tokens and timing. For Claude Code, spawned subagents have their own nodes. For Codex, child sessions connect to a parent when the rollout explicitly records that relationship.
Use this view to locate the part of a session you want to inspect. To decide whether a fix works, read the diff and run the relevant checks. A completed tool call is evidence of activity, not proof that the assignment is correct.
Is this view saving me a trip through the tabs?
Continue your normal work for one task cycle. When an agent stops, use ccdeck to orient yourself, return to the appropriate terminal, and review its result.
Then judge the dashboard against something concrete: could you identify the session and its recent activity before scrolling through its terminal? Did the waiting list point you to a Claude Code session you needed to answer?
That is a more useful trial than opening a dashboard and deciding whether the graph looks impressive.
Keep it if it earns its space
If you work in one session and already know exactly where it stands, another view may add little. If you alternate between Claude Code and Codex CLI, or regularly leave several sessions working, try the exercise with your next pair of tasks.
ccdeck is free under AGPL-3.0. It needs no ccdeck account, and your existing agent subscriptions or API access remain separate.
Closing the terminal does not stop the dashboard. Use npx ccdeck --stop when you want it off; npx ccdeck --uninstall removes its integrations. The README explains the local files that remain and the separate purge option.
Try ccdeck, keep your terminals, and see whether the shared view helps you get back to the right task.
Top comments (0)