hermes doctor
Diagnose config and dependency issues.
Diagnose config and dependency issues.
Exit status: 0 when the report lists no unresolved problems, 1 when at least one remains (including problems --fix could not repair), so a health gate or CI step can trust hermes doctor as a check.
The API Connectivity section includes an IPv6 route check: it opens one short (2 s) IPv6 TCP connection to a known dual-stack host. A route that is advertised but only times out (a blackholed IPv6 prefix) is reported as a warning naming the remedy, network.force_ipv4: true. Having no IPv6 route at all is healthy and reported as OK; the check is skipped when force_ipv4 is already set.
Custom-endpoint config checks (both warn-only; --fix does not rewrite them):
Config Structure also flags any list/mapping setting stored as one quoted string (plugins.enabled: '["a","b"]', model_catalog.excluded_providers: '["openai-api"]' — the shape older config set versions wrote): every reader ignores such a string, so the plugins silently stay unmounted and the exclusion never applies. The finding names the key and the hermes config set <key> '<literal>' command that stores a real list; the same warning appears in the startup banner. --fix does not rewrite the file.
From the official Hermes Agent CLI reference.
hermes doctor