Agent View and ccdeck: what each one shows

Checked on 5 November 2026 against ccdeck 3.81.3 and the sources below

Short answer

Use Agent View to start background Claude Code sessions and reply to them, and ccdeck to watch the sessions in every terminal, each subagent and Codex, without changing how you start them.

Agent View (claude agents) lists your background sessions, the ones that need input near the top, and lets you reply or start new ones.
ccdeck shows the Claude Code sessions from every terminal, each subagent as its own card, and Codex CLI sessions. It cannot reply: you answer in the terminal.

Side by side

Agent View as Anthropic’s documentation described it on 5 November 2026, and ccdeck as of 3.81.3:

Aspect	Agent View	ccdeck
Sessions in other terminals	Agent View: Only once you background them, with `/bg` or `←`.	ccdeck: Yes, whichever terminal started them.
Subagents	Agent View: Not as rows of their own.	ccdeck: Each Claude Code subagent is a card, joined to its session by a line.
Codex	Agent View: No, it lists Claude Code sessions.	ccdeck: Yes, read from Codex CLI’s own rollout files.
Waiting on you	Agent View: A Needs input group near the top, for questions, permission decisions and other prompts only you can answer.	ccdeck: Claude Code only: prompts and questions first in its session list, then finished turns, and its topbar names those stopped on a prompt or question. More in how to tell when Claude Code is waiting for input.
Reply or steer	Agent View: Yes, from the list or by attaching.	ccdeck: Only Continue on a stopped background session, and continuing a Codex task it moves between accounts.
Where it runs	Agent View: In your terminal, with a background supervisor running the sessions.	ccdeck: In a browser tab on your machine, or its desktop app; sessions stay where you started them.
Cost and quota	Agent View: No spend or quota in the list, and its documentation warns that background sessions “consume your subscription usage the same as interactive sessions.”	ccdeck: An estimated spend per session and per model, and Claude and Codex quota windows.
Accounts	Agent View: Its sessions use “the same stored credentials as your interactive sessions.”	ccdeck: An Accounts panel to sign in, switch and move Claude and Codex accounts, Claude’s through claude-swap.

What Agent View does that ccdeck does not

Agent View is Claude Code’s own screen for background sessions: “what's running, what needs your input, and what's done.” In claude agents:

Type a task and press Enter to start a background session, or run claude --bg with a prompt from your shell.
Press Space on a row to read the question it is waiting on and how long it has waited, and type a reply.
Press → to attach to the whole conversation, and ← to leave it running.
Sessions keep working with the terminal closed, and by default, in a git repository, each one edits files in its own worktree.

What it misses. In Anthropic’s words, “Interactive sessions you have open in other terminals don't appear until you background them,” and “Subagents and teammates a session spawns aren't listed as separate rows.” Agent View is a research preview.

What ccdeck shows that Agent View does not

ccdeck is a free, open-source dashboard that runs on your machine. Its first run adds a hook to ~/.claude/settings.json, so every Claude Code session that reads that file reports to it, from any terminal. You start sessions as you do now.

npx ccdeck --ref=agent-view

Each subagent Claude Code starts gets its own card, joined to its session, with its latest tool calls beside it. Double-click a card to read its tool calls in a side panel.
Codex CLI sessions are read from Codex’s rollout files, with no hook.

What it misses. It cannot answer, start or attach to a session: its hook only forwards events, so you reply in its terminal. Continue only resumes a background session stopped by an expired login or usage limit. The waiting list is Claude Code only, because Codex writes no approval request to its rollout files; a running Codex session that can ask for one shows approvals not visible instead. A Codex child session gets a card only if its rollout names its parent.

Use both

ccdeck’s hook answers nothing, so it cannot change what Agent View or its sessions do. A background session “reads its settings from the directory it runs in, the same as if you had started claude there,” and the hook is in your user settings, so the sessions Agent View runs reach ccdeck too.

For a session Agent View runs, ccdeck also shows Claude Code’s own line: the question it is stuck on and the reply Claude Code suggests, or the headline of what it got done.

Dispatch and reply in Agent View. Keep ccdeck open for the sessions in your other terminals, every subagent, Codex, and what they all spend.

Step by step

Sources

Read on 5 November 2026. What ccdeck does is checked against ccdeck 3.81.3, and what another tool does against its own documentation.