Goal: make agmsg delivery health visible before adding auto-recovery. This fork should support the existing Codex Desktop / Claude Desktop workflow, not require moving agents into the agmsg desktop app PTY.\n\nProblem: watcher / monitor / waker processes can disappear, become stale, fail silently, or remain as orphaned processes. The user should not need to ask each session whether its delivery path is alive.\n\nInitial scope: read-only / report-only visibility. Show registered agents, team, project, type, delivery mode, watcher/monitor/waker state, last check time, last notified message id when available, related PID/process hints, stale suspicion, orphan suspicion, Codex automation active/paused state, Windows Scheduled Task state when relevant, and agmsg core version.\n\nOut of scope for first slice: automatic kill, automatic restart, Desktop app internal IPC probing, replacing existing Codex Desktop / Claude Desktop sessions, or requiring app-owned PTY sessions.\n\nAcceptance criteria: one command or lightweight viewer can answer: who is registered, which delivery paths appear alive, which paths are stale or missing, and what manual action is recommended next. The implementation must use official agmsg scripts/APIs where available and avoid direct DB/team mutation.
Goal: make agmsg delivery health visible before adding auto-recovery. This fork should support the existing Codex Desktop / Claude Desktop workflow, not require moving agents into the agmsg desktop app PTY.\n\nProblem: watcher / monitor / waker processes can disappear, become stale, fail silently, or remain as orphaned processes. The user should not need to ask each session whether its delivery path is alive.\n\nInitial scope: read-only / report-only visibility. Show registered agents, team, project, type, delivery mode, watcher/monitor/waker state, last check time, last notified message id when available, related PID/process hints, stale suspicion, orphan suspicion, Codex automation active/paused state, Windows Scheduled Task state when relevant, and agmsg core version.\n\nOut of scope for first slice: automatic kill, automatic restart, Desktop app internal IPC probing, replacing existing Codex Desktop / Claude Desktop sessions, or requiring app-owned PTY sessions.\n\nAcceptance criteria: one command or lightweight viewer can answer: who is registered, which delivery paths appear alive, which paths are stale or missing, and what manual action is recommended next. The implementation must use official agmsg scripts/APIs where available and avoid direct DB/team mutation.