hermes - 💡(How to fix) Fix [Bug]: Bedrock Auxiliary Models Not Persisting / Not Supported [2 comments, 2 participants]

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…
GitHub stats
NousResearch/hermes-agent#18907Fetched 2026-05-03 04:53:38
View on GitHub
Comments
2
Participants
2
Timeline
9
Reactions
0
Author
Timeline (top)
labeled ×6commented ×2marked_as_duplicate ×1

Error Message

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Code Example

Report       https://dpaste.com/GVZQKR543
  agent.log    https://dpaste.com/AFMU3LM2N
  gateway.log  https://dpaste.com/45MJ98V6J

---
RAW_BUFFERClick to expand / collapse

Bug Description

Auxiliary models configured to use Bedrock are not persisting across sessions, and the auxiliary client doesn't appear to fully support Bedrock as a provider.

Steps to Reproduce

1. Run hermes model → Configure auxiliary models → Select Bedrock provider
2. Configure a Bedrock model (e.g., anthropic.claude-sonnet-4-20250514)
3. Try using any auxiliary task (vision, compression, session_search, curator)
4. Exit and restart Hermes
5. Check config.yaml — auxiliary model config is missing or reset

Or
  1. select configure auxillary model in the dropdown menu
  2. add model name and api key.
  3. exit and restart herms
  4. Check config.yaml — auxiliary model config is missing or reset

Or

Manually add auxillary models in config using bedrock as a provider with api key

It resets and doesnt work.

Expected Behavior

Configured auxiliary models should persist in config.yaml and work for ALL auxiliary tasks:
- auxiliary.vision — vision/image analysis tasks
- auxiliary.compression — context compression/summarization
- auxiliary.session_search — session search functionality
- auxiliary.curator — curator/skill review tasks
- Any other auxiliary task slots

Actual Behavior

  • Configured Bedrock auxiliary models disappear after restart - The auxiliary client (agent/auxiliary_client.py) resolve_provider_client() only handles:
    • auto, openrouter, nous, openai-codex (or codex), custom, anthropic, copilot, gemini
    • zai, kimi-coding, minimax, minimax-cn (via custom provider normalization) - Bedrock is NOT in this list - When Bedrock is configured for auxiliary tasks, it falls back to "custom" which produces empty responses - This matches what was found in the hermes-agent skill docs under "Auxiliary models not working"

Additional Evidence I manually added specific auxiliary configurations to config.yaml multiple times: yaml attempting to route them to nvidia.nemotron-super-3-120b

Despite this, the system ignores the manual config and falls back to "auto" every time.

Environment
- Hermes version: [run hermes --version]
- Provider: Bedrock
- Platform: macOS/Linux/Windows

Relevant Code
- agent/auxiliary_client.py — resolve_provider_client() function (lines ~1938-2170)
- The function doesn't handle Bedrock as a valid provider for any auxiliary tasks
- Config migration in hermes_cli/config.py handles auxiliary.{vision,compression,session_search,curator}.{provider,model}

Affected Component

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

Messaging Platform (if gateway-related)

No response

Debug Report

Report       https://dpaste.com/GVZQKR543
  agent.log    https://dpaste.com/AFMU3LM2N
  gateway.log  https://dpaste.com/45MJ98V6J

Operating System

macOS Sequoia 15.7.4

Python Version

3.11.13

Hermes Version

v0.12.0

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

Suggested Fix
1. Add Bedrock support to resolve_provider_client() in agent/auxiliary_client.py
2. The Bedrock client should use boto3 / aws_sdk (as noted in recent PRs: "aux aws_sdk")
3. Ensure auxiliary config persists properly in config.yaml when using Bedrock
4. Test all auxiliary task slots: vision, compression, session_search, curator

References
- Related PRs:
  - #10569, #15184, #15366 — fixes for Bedrock including "aux aws_sdk, stale-connection eviction"
  - These PRs added Bedrock support to the MAIN provider but NOT to the auxiliary client
- Docs reference: https://hermes-agent.nousresearch.com/docs/user-guide/configuration
- Related issue: #11946 — "Support AWS Bedrock as auxiliary LLM provider"

Are you willing to submit a PR for this?

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

extent analysis

TL;DR

The most likely fix is to add Bedrock support to the resolve_provider_client() function in agent/auxiliary_client.py to persist auxiliary model configurations across sessions.

Guidance

  • Review the resolve_provider_client() function in agent/auxiliary_client.py to understand how it handles different providers and add Bedrock as a valid provider.
  • Ensure the Bedrock client uses boto3 or aws_sdk as noted in recent PRs to properly handle auxiliary tasks.
  • Verify that auxiliary model configurations are persisted correctly in config.yaml when using Bedrock by manually adding configurations and checking after restart.
  • Test all auxiliary task slots (vision, compression, session_search, curator) to ensure they work as expected with Bedrock.

Example

No code example is provided as the issue requires modification of existing code in agent/auxiliary_client.py, which is not included in the issue body.

Notes

The fix requires modifying the resolve_provider_client() function to support Bedrock, which is not currently handled. The issue is specific to the Hermes version v0.12.0 and may not apply to other versions.

Recommendation

Apply the workaround by adding Bedrock support to the resolve_provider_client() function, as this is the most direct way to address the issue. This will require modifying the existing code to handle Bedrock as a valid provider for auxiliary tasks.

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…

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 - 💡(How to fix) Fix [Bug]: Bedrock Auxiliary Models Not Persisting / Not Supported [2 comments, 2 participants]