claude-code - 💡(How to fix) Fix [DOCS] Background-session docs omit `claude daemon status` diagnostics [1 participants]

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/cli-reference

Section/Topic

CLI and troubleshooting documentation for background-session daemon diagnostics

Current Documentation

The docs currently list the background-session commands:

claude agents | Open agent view to monitor and dispatch parallel background sessions.

claude attach <id> | Attach to a background session in this terminal

claude logs <id> | Print recent output from a background session

claude respawn <id> | Restart a stopped background session with its conversation intact

claude rm <id> | Remove a background session from the list

claude stop <id> | Stop a background session

And the agent-view docs say:

Session state is stored under your Claude Code config directory.

~/.claude/daemon.log | Supervisor log

~/.claude/daemon/roster.json | List of running background sessions, used to reconnect after a restart

What's Wrong or Missing?

The v2.1.141 release notes indicate that claude daemon status is a supported diagnostic command and that /doctor uses the same daemon state on Windows, but the docs do not document claude daemon status anywhere.

That leaves a gap in the background-session troubleshooting story: the docs describe the supervisor, its on-disk files, and adjacent commands such as claude logs, but they do not tell users that there is a daemon-status command they can run to inspect this subsystem directly.

Because the v2.1.141 fix specifically improves how Windows users see locked or unreadable daemon pipe-key file errors, that diagnostics path is now user-visible but still undocumented.

Suggested Improvement

Add claude daemon status to the CLI reference and link to it from the background-session/agent-view troubleshooting docs.

The new entry should explain what subsystem it checks, when to use it instead of or alongside /doctor, and note that on Windows v2.1.141 and later it surfaces the underlying daemon pipe-key file access error instead of a generic failure.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

Total scope: 3 pages affected

Version context: v2.1.141 release notes say claude daemon status and /doctor on Windows now surface the underlying daemon pipe-key file error when that key file is locked or unreadable.