doctor · git:20261001.84b0696 · 2026-10-01 · sha256 b12f624d99ab11cf
doctor git:20261001.84b0696A
Immutable. This exact content never changes and is served at /api/v1/blob/b12f624d99ab11cf.
--- name: doctor description: Health probe across Captain Memo's components — embedder service, worker service, config, plugin registration, plugin manifest. Use when the user types /captain-memo:doctor or when something seems wrong. --- # Captain Memo — doctor (health probe) When invoked, run a comprehensive health check and report PASS/WARN/FAIL for each component, with one-line remediation hints when something's not green. ## What to do The CLI has the canonical implementation. Just shell out: ```bash captain-memo doctor ``` …and pass the output back to the user verbatim (it's already nicely formatted with colour and remediation hints). If `captain-memo` isn't on PATH, fall back to the shim the installer wrote: ```bash ~/.local/bin/captain-memo doctor # user install; /usr/local/bin/captain-memo in --system mode ``` …or run `bun ./bin/captain-memo doctor` from the checkout — its path is the `installLocation` of `captain-memo` in `~/.claude/plugins/known_marketplaces.json`. ## On error If even the CLI invocation fails, that's a sign something is broken at the install layer. Suggest: ```bash ls ~/.claude/plugins/captain-memo ``` …and look at the worker's service. On Linux: `systemctl --user list-units 'captain-memo-*'` (a `--system` install: without `--user`). On macOS: `launchctl print gui/$(id -u)/com.captainmemo.worker`. On Windows (PowerShell): `Get-ScheduledTask -TaskName 'captain-memo-worker'`. That shows whether the install ever happened; run `captain-memo install` if not.