claude agents: See Which Background Sessions Need Your Attention, From One Terminal

claude agents shows every background Claude Code session grouped by state — "Needs input" (yellow ✻) is the priority queue; Space lets you peek and reply without leaving the list.

When you're running multiple background sessions via --bg, /fork, or a Workflow fan-out, you can't tell which ones are blocked without reattaching to each one. claude agents solves that:

claude agents
# optional flags:
# --cwd ~/projects/my-app   scope to one directory
# --model opus              set dispatch defaults

Sessions group by state. The three that matter:

State	Icon	What to do
Needs input	Yellow ✻	Reply — Claude is blocked
Working	Animated	Leave it running
Completed	Green ✓	Peek to read the result

Navigate without fully attaching:

• Space opens a peek panel. Read the context, compose a reply, press Enter — Claude unblocks without you leaving the session list.
• Enter or → attaches to the full interactive conversation.
• ← detaches and returns to the list.

Dispatch from the view: type a task description in the input bar and press Enter. A new background session spins up alongside the existing ones. Use Shift+Enter to dispatch and attach immediately.

Other keybindings worth knowing:

• Ctrl+T — pin a session (prevents the 1-hour idle shutdown)
• Ctrl+R — rename a session
• Ctrl+X — stop; press twice to delete
• ? — full shortcut list

Stated limits: Each background session draws on your rate-limit quota independently — 10 parallel sessions use roughly 10× your normal per-session rate. Non-pinned idle sessions stop after ~1 hour. The interface is still labeled research preview; shortcuts may change between releases.

The practical pattern: keep claude agents open in a split pane during a multi-agent run. Every yellow ✻ is a decision waiting for you; everything else is running fine.

Sources: Agent view docs — code.claude.com, Claude Code v2.1.234 changelog