2026-07-21 13:35:51 -05:00
---
description: Check CHORUS readiness — Python, vault reachability, auth, bootstrap/schema, and key source
---
Use the **chorus-memory** skill to run a one-call readiness check before relying on memory.
```bash
CHORUS = " ${ CLAUDE_PLUGIN_ROOT } /skills/chorus-memory/scripts/chorus.py"
[ -f " $CHORUS " ] || CHORUS = $( ls /sessions/*/mnt/.remote-plugins/*/skills/chorus-memory/scripts/chorus.py 2>/dev/null | head -1) # CoWork sandbox fallback
python3 " $CHORUS " doctor
# Windows: use `python` or `py -3` if `python3` is not on PATH.
```
It prints green/red for: Python version, vault reachability, auth accepted, vault
bootstrapped (+ `schema_version` ), and the **config source** for owner/endpoint/key
(per-field: env override `CHORUS_OWNER` /`CHORUS_BASE` /`CHORUS_KEY` , then the machine-local
`~/.claude/chorus-memory/config.json` — or `baked-in (plugin)` on a per-user baked build,
which is authoritative and reported as such). Exits non-zero if anything is red — if the config is
2026-07-21 15:41:58 -05:00
missing (or still the placeholder template), ask the member for their chorus-memory config file and install it with `chorus.py config import <path>` (or `config set --owner … --endpoint … --key …` ). For the full vault-invariant lint, run
2026-07-21 13:35:51 -05:00
`/chorus-health` .