Description
The hermes setup wizard shows "not configured" for Web search (Firecrawl), Image generation (FAL), and Browser automation (Browser Use) even after selecting "Enable for all tools" and having use_gateway: true correctly set in config.yaml.
The wizard appears to check only for individual API keys in .env (FIRECRAWL_API_KEY, FAL_KEY, BROWSERBASE_API_KEY) and does not account for Nous subscription gateway mode.
Steps to Reproduce
- Be a Nous subscriber
- Run
hermes setup
- At the Tool Gateway prompt, select "Enable for all tools"
- Exit setup
- Run
hermes setup again
- Observe: all gateway-managed tools still show "not configured"
Expected Behavior
Tools using Nous subscription gateway should show a status like:
- ✅ Nous Gateway (subscription)
- or similar, indicating the tool is active via the subscription
Actual Behavior
All tools show:
- ○ Web search & extract (Firecrawl) — not configured
- ○ Image generation (FAL) — not configured
- ○ Browser automation (Browser Use) — not configured
Investigation
The config.yaml already contains the correct gateway settings:
web:
backend: firecrawl
use_gateway: true
image_gen:
use_gateway: true
browser:
cloud_provider: browser-use
use_gateway: true
The tools work correctly in practice — web_search, image_generate, and browser_* tools all function via the Nous gateway. The issue is purely the setup wizard UI not reflecting the actual configuration state.
Root Cause
The setup wizard's tool status check (likely in setup_tools() in hermes_cli/setup.py) checks for individual API keys in .env but does not check config.yaml for use_gateway: true flags. It should recognize that gateway mode is a valid configured state.
Related
Environment
- OS: macOS
- Hermes Version: latest (as of 2026-04-21)
- Provider: Nous subscription
- Tools affected: web_search (Firecrawl), image_gen (FAL), browser (Browser Use)
Description
The
hermes setupwizard shows "not configured" for Web search (Firecrawl), Image generation (FAL), and Browser automation (Browser Use) even after selecting "Enable for all tools" and havinguse_gateway: truecorrectly set in config.yaml.The wizard appears to check only for individual API keys in
.env(FIRECRAWL_API_KEY, FAL_KEY, BROWSERBASE_API_KEY) and does not account for Nous subscription gateway mode.Steps to Reproduce
hermes setuphermes setupagainExpected Behavior
Tools using Nous subscription gateway should show a status like:
Actual Behavior
All tools show:
Investigation
The config.yaml already contains the correct gateway settings:
The tools work correctly in practice —
web_search,image_generate, andbrowser_*tools all function via the Nous gateway. The issue is purely the setup wizard UI not reflecting the actual configuration state.Root Cause
The setup wizard's tool status check (likely in
setup_tools()inhermes_cli/setup.py) checks for individual API keys in.envbut does not checkconfig.yamlforuse_gateway: trueflags. It should recognize that gateway mode is a valid configured state.Related
hermes doctorreporting misleading status for image_gen (same root cause: commit 95dc9aa removed requires_env metadata without adding gateway-aware status)Environment