Issue Station
Sign In
Tools hereToolbox

hermes - ✅(Solved) Fix [Bug]: hermes setup shows "not configured" for gateway-managed tools even when use_gateway=true [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

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.

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.

Fix Action

Fixed

PR fix notes

PR #13327: fix(setup): recognize gateway-managed tools

Description (problem / solution / changelog)

Summary

  • Fixes #13301
  • Treats tts.use_gateway, browser.use_gateway, web.use_gateway, and image_gen.use_gateway as configured tools in setup summaries
  • Keeps direct-key summaries intact, while preferring the gateway label for sections explicitly routed through the Nous Tool Gateway

Root Cause

hermes setup only looked for direct provider API keys such as FIRECRAWL_API_KEY and BROWSERBASE_API_KEY when deciding whether the tools section was configured. Gateway-managed tools persist intent in config via use_gateway: true, so they were incorrectly reported as unconfigured.

Tests

  • uv run --frozen --python 3.11 --extra dev pytest -o addopts='' tests/hermes_cli/test_setup.py -q (20 passed)
  • git diff --check -- hermes_cli/setup.py tests/hermes_cli/test_setup.py

Changed files

  • hermes_cli/setup.py (modified, +21/-3)
  • tests/hermes_cli/test_setup.py (modified, +37/-0)

Code Example

web:
  backend: firecrawl
  use_gateway: true
image_gen:
  use_gateway: true
browser:
  cloud_provider: browser-use
  use_gateway: true
RAW_BUFFERClick to expand / collapse

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

  1. Be a Nous subscriber
  2. Run hermes setup
  3. At the Tool Gateway prompt, select "Enable for all tools"
  4. Exit setup
  5. Run hermes setup again
  6. 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

  • #9516 — Similar issue with hermes doctor reporting misleading status for image_gen (same root cause: commit 95dc9aa removed requires_env metadata without adding gateway-aware status)

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)

extent analysis

TL;DR

The setup wizard needs to be updated to recognize the Nous subscription gateway mode as a valid configuration state, checking config.yaml for use_gateway: true flags instead of only individual API keys in .env.

Guidance

  • Review the setup_tools() function in hermes_cli/setup.py to understand how the tool status check is currently implemented.
  • Modify the status check to also consider the use_gateway: true flags in config.yaml as a valid configuration state.
  • Verify that the setup wizard correctly reflects the actual configuration state by running hermes setup after applying the changes.
  • Consider updating the hermes doctor command to also recognize gateway mode as a valid configuration state, as it has a similar issue (related to #9516).

Example

# Example of how the setup_tools() function could be modified
def setup_tools():
    # ... existing code ...
    for tool in tools:
        if tool['use_gateway']:
            # Mark the tool as configured if use_gateway is True
            tool['status'] = 'configured'
        # ... existing code ...

Notes

The provided solution assumes that the setup_tools() function is responsible for checking the tool status and that modifying this function will fix the issue. However, without the actual code, this is an educated guess.

Recommendation

Apply workaround: Modify the setup_tools() function to recognize the Nous subscription gateway mode as a valid configuration state, as this is a more targeted solution than waiting for a potential future upgrade.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#dependency error#configuration error#environment variable#network issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - ✅(Solved) Fix [Bug]: hermes setup shows "not configured" for gateway-managed tools even when use_gateway=true [1 pull requests]