Common Harness Errors

Harness Not Actually Installed

Signal: ORCA docs are present, but the harness commands or UI are unavailable.

Fix: install or open the harness first.

Capability Assumption Mismatch

Signal: the harness cannot do something ORCA can do elsewhere.

Fix: use compatibility-matrix.md and degrade gracefully.

Wrong Verification Target

Signal: the user validates ORCA itself but not the host they plan to use.

Fix: run doctor with --harness.

Local Codex Config Noise

Signal: Codex prints unrelated local skill-load or memory-database errors before the real run starts.

Fix: prefer the installed orca or orca-* wrappers for Codex runs, because they use codex exec --ignore-user-config to isolate ORCA from broken local Codex config.