What problem does it solve?
CoPaw deployments can fail in many ways—unresponsive daemons, disconnected channels, failed model calls, stalled cron jobs, or broken multi-agent workspaces—and operators need a structured runbook instead of guessing which restart command to run.
Core Features & Use Cases
- Guided Diagnosis: Runs a minimal closed-loop check (daemon status, agent list, models, channels, cron, logs) before any recovery action.
- Fault Triage by Symptom: Routes issues into distinct branches for service outages, channel disconnects (DingTalk, Feishu, QQ), model failures, cron problems, and built-in skill loading errors.
- Safe High-Impact Operations: Requires user confirmation before restarts, reloads, forced init, workspace deletion, or config changes.
- Use Case: When a DingTalk channel stops receiving messages, the skill checks channel config fields, verifies robot publication status, and restarts the daemon only after confirming with the operator.
Quick Start
Ask the assistant to check why the CoPaw service is not responding and follow its diagnosis steps.