Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix hermes config set model.* does not update nested dict config

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…

hermes config set model.default deepseek-v4-flash sets individual keys at the top level of config.yaml, but the model section is stored as a nested dict. The individual keys get overwritten by the existing dict block, so the change has no effect.

Root Cause

hermes config set model.default deepseek-v4-flash sets individual keys at the top level of config.yaml, but the model section is stored as a nested dict. The individual keys get overwritten by the existing dict block, so the change has no effect.

Code Example

model:
  default: glm-5-turbo
  provider: zai
  base_url: https://open.bigmodel.cn/api/coding/paas/v4
  context_length: 200000

---

hermes config set model.default deepseek-v4-flash
hermes config set model.provider deepseek
RAW_BUFFERClick to expand / collapse

Description

hermes config set model.default deepseek-v4-flash sets individual keys at the top level of config.yaml, but the model section is stored as a nested dict. The individual keys get overwritten by the existing dict block, so the change has no effect.

Steps to Reproduce

  1. Config has model configured as nested dict:
model:
  default: glm-5-turbo
  provider: zai
  base_url: https://open.bigmodel.cn/api/coding/paas/v4
  context_length: 200000
  1. Run:
hermes config set model.default deepseek-v4-flash
hermes config set model.provider deepseek
  1. hermes config show still shows the old values (glm-5-turbo / zai)

Expected Behavior

hermes config set model.default should update the value inside the nested model dict in config.yaml, not set a separate top-level key.

Environment

  • Hermes version: (latest main branch)
  • OS: Ubuntu Linux
  • Config path: ~/.hermes/config.yaml

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 hermes config set model.* does not update nested dict config