overview / commands / rabadon doctor
rabadon doctorHealth check: native binaries built, binary/package version lockstep, kernel sandbox backend, global hook health (every hook command in the user settings file Claude Code reads — $CLAUDE_CONFIG_DIR/settings.json when that is set, else ~/.claude/settings.json — points at a file that exists and belongs to this install), claude CLI presence, spool size and retention.
maturity: stable — shipping and tested
The binary check knows what the core is by reading the Makefile — every target make all produces, plus every explicit native/rabadon-* rule — so a binary added to the build is a binary doctor checks for, with nothing to keep in sync. Any that are absent are listed by name: an absent binary is a command that fails when you run it, not when you install it, and a partial source build (make stopped on one target) still reports install success. If the Makefile cannot be read, doctor says so and refuses to certify rather than reporting green.
Exit: 0 all green · 1 at least one thing to look at.
The gate is not firing — why? · How much disk does the ledger use? · The install didn't build the binary — what now? · What if rabadon itself crashes? · The sandbox says no backend — what do I install?
rabadon doctor reported the native core green by…