[Bug]: API key and provider ignored

[rkondratowicz]

Bug Description

Hermes doesn't seem to use the settings for Opencode Go (possibly other)

I've repeated the setup process several times with no luck.

Running the doctor shows:

◆ Configuration Files
  ✓ ~/.hermes/.env file exists
  ✓ API key or custom endpoint configured
  ✓ ~/.hermes/config.yaml exists

but also:

◆ API Connectivity
  ⚠ OpenRouter API (not configured)

Is OpenRouter key required for Hermes to start?

Steps to Reproduce

1. Run hermes setup
2. Select OpenCode Go as the provider
3. Provide API key
4. Pick model
5. Finish the setup
6. Run hermes to start chatting
7. Error appears:

It looks like Hermes isn't configured yet -- no API keys or providers found.

Expected Behavior

Hermes recognises the configuration for OpenCode

Actual Behavior

It looks like Hermes isn't configured yet -- no API keys or providers found.

  Run:  hermes setup

Run setup now? [Y/n]

Affected Component

Setup / Installation

Messaging Platform (if gateway-related)

N/A (CLI only)

Operating System

Ubuntu 24.04.3 LTS

Python Version

3.11.15

Hermes Version

v0.4.0 (2026.3.18)

Relevant Logs / Traceback

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

• I'd like to fix this myself and submit a PR

[LucasUTNFRD]

I fixed this locally by following this #1984.

[Moranilt]

same error for me. I've setup a local model with openai compatible endpoint. And I've got the same error.

It looks like Hermes isn't configured yet -- no API keys or providers found.

[bboyles303]

Also getting It looks like Hermes isn't configured yet -- no API keys or providers found. on a fresh setup. Model and provider are in config.yaml but can't start

[thegreatzach]

I was also having an issue with this on fresh install. Doing some digging I think this function is the culprit. It looks in the .env specifically for:

provider_env_vars = {"OPENROUTER_API_KEY", "OPENAI_API_KEY", "ANTHROPIC_API_KEY", "ANTHROPIC_TOKEN", "OPENAI_BASE_URL"}

These keys do not seem to be configured when running through setup with a custom endpoint. Maybe because no api key was defined? I added to ~/.hermes/.env

OPENAI_BASE_URL=http://localhost/v1
OPENAI_API_KEY=

This allowed me to chat with my local instance of llama.cpp. This seems to only be an issue with the Chat TUI as using a custom provider with the gateway to mattermost worked fine for me with out this .env change.