Version: v5.6.1

opschain doctor

Included from Basic tier

opschain doctor [server|runner]

Check this host's prerequisites and optional capabilities — a local probe, no server contact. Each capability prints as ok, MISSING (required) or missing (optional) with a detail column; -o json|yaml emits the same list as a document.

The optional role narrows the probe set to one deployment role:

Invocation	Probes	Rationale
`opschain doctor server`	git, opschain home writability, OS keychain	A server never executes actions, so none of the execution-toolchain probes run.
`opschain doctor runner`	ruby, bundler, container runtime, MintPress SDK, home, keychain	Ruby, bundler and the MintPress SDK are probed as optional capabilities — only applicable to existing MintPress customers and those using the MintPress SDK or the `packs:mintpress` feature; a container runtime matters only for containerexec.
`opschain doctor`	everything	The combined local-development view.

The hard requirements are git >= 2.35 (probed for the server and combined views) and a writable opschain home (the resolved --home / OPSCHAIN_HOME, probed in every view); everything else is optional with role-accurate detail. The keychain probe is macOS-only in Phase 0 — elsewhere it reports the key-file fallback.

opschain doctor server
CAPABILITY  STATUS  DETAIL
git         ok      git version 2.43.0
home        ok      /Users/op/Library/Application Support/opschain is writable
keychain    ok      macOS keychain via /usr/bin/security

Named errors

unknown doctor role "<role>" (expected server or runner) — exit 2.
required capabilities missing: <names> — printed after the table when a required capability is absent; exit 1.

Exit codes

Code	Meaning
0	Every required capability is present (optional ones may be missing).
1	A required capability is missing, or probing failed.
2	Usage error — unknown role or stray arguments.

Named errors​

Exit codes​

See also​

Named errors

Exit codes

See also