Backend Auth Troubleshooting
Run the backend doctor through the setup skill or directly from a checked-out skill:
bash skills/orcats-setup/scripts/orca-doctor.sh --backend codexThe doctor script is byte-identical in two skill directories — skills/orcats-setup/scripts/orca-doctor.sh and skills/orcats-flow/scripts/orca-doctor.sh. Either path works; prefer the orcats-setup copy (the canonical location) and keep the two in sync if you edit one.
Status meanings:
| Status | Meaning |
|---|---|
ready | CLI is present and auth is confirmed. |
unverified | CLI works, but auth cannot be proven without a live smoke. |
unauth | CLI is present but not authenticated. |
missing | CLI is not on PATH. |
misconfig | CLI is present but broken. |
Use backend-specific login tools such as codex login, opencode auth login, Claude login/setup, or Pi credentials, then rerun the doctor.
For Claude and Pi, the definitive proof is the opt-in live smoke because there is no safe non-spending auth check.