hermes - 💡(How to fix) Fix Support AUTH_JWT_SECRET for local (self-hosted) Honcho instances

Problem

When configuring Hermes against a self-hosted (local) Honcho instance, the honcho setup flow does not configure AUTH_JWT_SECRET. This appears intentional based on the setup output, but it forces users to set AUTH_USE_AUTH=false to run a local instance — leaving the Honcho API entirely unauthenticated.

Expected Behavior

AUTH_JWT_SECRET should be configurable regardless of whether the Honcho provider is cloud or local. JWT is transport-agnostic and there is no architectural reason to restrict it to cloud deployments.

Current Workaround

Set AUTH_USE_AUTH=false in the Honcho compose environment, which disables all authentication on the local instance.

Suggested Fix

During hermes honcho setup, when the user selects a local/self-hosted provider:

• Prompt for (or auto-generate) an AUTH_JWT_SECRET, the same way the cloud path does, or
• Document that users must set this manually and validate it during setup

Impact

Users self-hosting Honcho who want authenticated API access have no supported path to configure it through Hermes tooling.