---
description: Check rdbg daemon connectivity, active sessions, and surface common issues (Session 0, busy daemon).
---

Call the `mcp__rdbg__status` MCP tool. Format the response for the
user with:

- **Daemon connection:** version + protocol + active session count.
- **Current session(s):** for each session, show `session_id`,
  `pid`, `state` (running/paused/detached/exited), `bp_count`,
  and `last_pause` (file:line if available).
- **Diagnostics:** flag these specific issues if present —
  - **Daemon in Session 0** — call `mcp__rdbg__hello` and check
    `session_id` if reported. If 0, warn that `capture_window`
    will return blank pixels and the user should relaunch
    Claude Code from inside their interactive RDP desktop.
  - **No active session** — that's fine; suggest `attach` or
    `launch` to start one.
  - **Daemon unreachable** — surface `/rdbg:start-daemon` and
    stop. Don't try to diagnose further; the daemon isn't
    listening.

Keep the output to ~10 lines. The user invokes this when they
want a quick health check, not a wall of text.
