hermes doctor
Hermes doctor output decoder
Turn Hermes doctor, install, update, and package errors into a repair path.
What this workflow solves
Errors such as missing packages, stale virtual environments, node visibility, and provider response crashes are easy to misdiagnose when they appear after updates.
How the check works
Paste non-secret doctor or install output.
Classify environment, package, provider, gateway, and dashboard risks.
Generate a repair plan with the safest next command group.
Common risks to catch early
- Stale Python venv after update
- Missing dashboard package modules
- Node hidden by mise, asdf, nvm, or Homebrew shims
- Provider errors redacted too late at HTTP boundaries
Sample readiness receipt
Status: Needs fixes before production users depend on this route.
Evidence: Workspace notes mention the target surface, but do not yet prove callback host, tool visibility, secret handling, and operator handoff.
Recommended next action: Run the console, save the result, and unlock the complete Team report when the setup is ready for review.