Direct answer
Hermes WebUI onboarding is successful only when the wizard, provider configuration, model readiness, workspace path, and chat endpoint line up. A partial setup can still show a UI while chat is blocked or a different state directory is being used.
When this matters
- An install reaches the wizard but chat is not ready.
- Provider configuration exists but the selected model or base URL is not usable.
- A team wants a redacted support report without pasting secrets into a public channel.
How to handle it
- Paste a redacted onboarding status summary and non-secret health result.
- Check completed state, provider readiness, model selection, and intended state directory.
- Separate human-owned credential steps from assistant-safe diagnostic steps.
- Generate a support-ready report that excludes tokens, cookies, and private paths.
Common risks
- Full environment files can leak credentials if copied into reports.
- A provider can be configured but not chat-ready if model discovery fails.
- A real Hermes home should not be deleted or overwritten during onboarding trials.
How Launch Lab connects
Launch Lab turns redacted onboarding evidence into a clear pass, fail, or waiting-on-human status.