hermes - 💡(How to fix) Fix Bug: Config accumulates multiple model entries after running hermes model multiple times

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…

After running hermes setup or hermes model multiple times, the config.yaml file accumulates multiple model configuration entries instead of overwriting the previous ones.

Error Message

  1. Warn when configuration accumulation is detected

Root Cause

Actual Behavior

  • Multiple model entries accumulate in the yaml file
  • It is unclear which configuration is read at startup, priority is not defined
  • Because the first URL has a typo, the entire model connection fails
RAW_BUFFERClick to expand / collapse

Description

After running hermes setup or hermes model multiple times, the config.yaml file accumulates multiple model configuration entries instead of overwriting the previous ones.

Steps to Reproduce

  1. Run hermes model to configure a model (e.g., GLM, with a typo in URL like http://xxx.cm)
  2. Run hermes model again to configure another model
  3. Check ~/.hermes/config.yaml - you will find multiple model configuration entries

Expected Behavior

  • Each run of hermes model should overwrite the previous model configuration, not append
  • Or at least clearly inform the user about the current configuration and priority

Actual Behavior

  • Multiple model entries accumulate in the yaml file
  • It is unclear which configuration is read at startup, priority is not defined
  • Because the first URL has a typo, the entire model connection fails

Environment

  • OS: Linux
  • Hermes version: Latest

Suggestions

  1. Show current configuration status after each setup/model command
  2. Warn when configuration accumulation is detected
  3. Document the configuration priority/load order clearly

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