server-doctor

What problem does it solve?

Server Doctor helps operators audit and repair Linux or macOS hosts running OpenClaw gateways and Telegram-facing automation by first building an environment map, then performing evidence-bound diagnostics, classification, and safe remediation guidance without exposing secrets.

Core Features & Use Cases

• Access-first environment mapping: collects a minimum inventory (hosts, bots/services, runtime owners, paths, and safe connection methods) and runs in mapped, partial map, or unreachable modes.
• Runtime discovery and service identification: detects how workloads are started and supervised across systemd, launchd, Docker/Compose, direct processes, and terminal multiplexers.
• Incident-ready, evidence-bounded diagnosis: structures diagnosis around spec correctness vs ops quality, uses evidence hierarchy, and applies strict “anti-false-outage” wording discipline.
• Operational map outputs: produces host-by-host maps, bot-to-host maps, user-by-user runtime inventories, access maps, restart/log/status commands, risks, and known unknowns.
• Public-safe documentation and incident helpers: instructs redaction of sensitive data and references incident/health/outage classification rules and scenario playbooks.

Quick Start

Ask Server Doctor to audit a specific host by first providing which machines run which OpenClaw/Telegram services, the Unix owner/account, the likely runtime style (systemd/launchd/Docker/direct), and the safe way to access each machine (such as SSH or tailscale).