`claude agents` banner hints "list sessions" but cmd only lists definitions (v2.1.139)

Status Fixed / completed
Reported on v2.1.139
Maintainer reply ✓ Yes — bogini
Activity 4 comments · opened May 12, 2026 · closed May 13, 2026
💡 Likely answer: A maintainer (bogini, collaborator) responded on this thread — see the highlighted reply below.

Summary

After backgrounding a session, the launch banner advertises claude agents as a way to "list sessions" — but running claude agents (or claude agents list) only prints the configured agent definitions. There is no documented subcommand or flag that lists active background sessions from a sibling shell.

Environment

  • Claude Code 2.1.139 (latest stable at time of report)
  • macOS Darwin 24.6.0
  • Single user, single daemon (/tmp/cc-daemon-502/95be5075/)
  • daemonColdStart: default (transient)

Repro

  1. From terminal A, start claude in a project directory and let it background (banner appears):

``
backgrounded · 52628302
claude agents list sessions
claude attach 52628302 open in this terminal
claude logs 52628302 show recent output
claude stop 52628302 stop this session
``

  1. Open a fresh terminal B (same user, same shell init).
  2. Run claude agents (or claude agents list, or claude agents --setting-sources user,project,local).

Expected

Output includes an "Active sessions" section listing the running backgrounded session(s), matching the banner hint. Ideally with the session ID, cwd, and status so claude attach <id> is discoverable.

Actual

17 active agents

User agents:
  architect · opus
  ...
Plugin agents:
  ...
Built-in agents:
  ...

Only configured agent definitions are printed. No session listing. claude agents list ignores the positional and prints the same output. claude --help lists no sessions / bg / background subcommand.

The daemon and bg session are clearly healthy — sockets exist under /tmp/cc-daemon-502/95be5075/{control.sock, pty/52628302.sock, rv/*.sock} and the panel is reachable from a foreground session (see workaround).

Workaround

From a foreground claude session:

  • Press ← to navigate into the FleetView agent panel, or
  • Run /tui default (or /tui fullscreen) — toggling the renderer re-mounts the TUI and lands on the panel since that was the last view.

Neither works from a sibling shell that has no foreground session.

Suggested fix

Either:

  1. Implement the list sessions behavior the banner advertises (likely the intent — the hint copy in the backgrounded banner is specific).
  2. Update the banner copy to point to whatever cmd actually lists sessions (or remove the line).

Either way the banner ↔ cmd contract should match so users can discover their own bg fleet without launching a foreground session first.

View original on GitHub ↗

4 Comments

ThatDragonOverThere · 5 months ago

Confirmed on v2.1.139 Windows. The banner suggests live session supervision — it is a config-listing command. This was one of five failure modes from an overnight autonomous run that burned 80% of weekly usage for zero completed work. Full incident report at #58450.

bogini collaborator · 5 months ago

Thanks for reporting. This was a feature-flag delivery issue — claude agents was gated on a GrowthBook flag whose cache could be stale or unreachable depending on platform/network. We've removed the gate entirely; claude agents now opens the dashboard unconditionally (including on Bedrock/Vertex/Foundry).

Ships in v2.1.141 (tomorrow).

claude[bot] contributor · 5 months ago

This issue was fixed as of version 2.1.141.

github-actions[bot] · 3 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.