ccdoing
Passive status page + watchdog for Claude Code sessions. Derives an ACTIVE/QUIET/DOWN/STUCK verdict from observed side effects (git, processes, task files) and can deliver the diagnosis into a provably stuck session as an informational nudge - never a resume or restart.
Plugin ccdoing from marketplace whats-cc-doing in nickjrotundo/whats-cc-doing. Commands read from the repo's manifest — 1 month ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
What it installs
Skills (6)
helpQuick ccdoing orientation - current status of the monitor, watchdog, and web server, plus the common commands with one-line descriptions.
liveWatch this project's ccdoing status live for the rest of the session and react when the verdict changes (goes QUIET, STUCK, or DOWN).
serveStart, restart, or stop the ccdoing status web server and hand the user the link - the all-projects dashboard by default.
setupSet up the What's CC Doing status monitor + watchdog for this project - inventory signals, write ccdoing.yaml, install the watchdog loop, verify the alert path end to end.
statusCheck what's happening in this project right now - read the ccdoing status snapshot, explain the verdict and any stalls, and say what (if anything) needs attention.
tuneRe-tune the What's CC Doing status monitor after the project changed - review config drift, propose signal deltas, apply approved changes, verify.
Hooks (1)
- SessionStart
command -v ccdoing >/dev/null 2>&1 && [ -f ccdoing.yaml ] && { ccdoing doctor --arm-check || true; ccdoing doctor --drift --quiet || true; } || true
Maintain ccdoing?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.