Bug Description

Version: v0.60

Description:

The fallback_model section in ~/.hermes/config.yaml does not work when configured manually following the comments in the config file itself. The comments show a list format with - but the code expects a plain object, causing an AttributeError: 'list' object has no attribute 'get' in config.py line 1457.

Additionally, even after fixing the list vs object format, manually setting OPEN_ROUTER_API_KEY in ~/.hermes/.env is not picked up correctly, resulting in persistent HTTP 401 "User not found" errors from OpenRouter despite a valid key.

The only working solution is running hermes setup which writes the config in a format the code actually accepts.

Steps to Reproduce

Edit ~/.hermes/config.yaml and add fallback_model following the commented example in the file
Add OPEN_ROUTER_API_KEY to ~/.hermes/.env manually
Restart gateway — fallback fails with 401
Run hermes setup instead — works immediately

Expected Behavior

Manual config editing should work as documented in the config file comments

Actual Behavior

AttributeError: 'list' object has no attribute 'get' and persistent 401 on fallback provider despite valid API key

Affected Component

Configuration (config.yaml, .env, hermes setup)

Messaging Platform (if gateway-related)

No response

Operating System

macOS 26.3.1

Python Version

3.11.3

Hermes Version

0.6.0

Relevant Logs / Traceback

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

Either fix the config comments to match what the code expects, or make save_config handle both list and object formats for fallback_model

Are you willing to submit a PR for this?

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