NousResearch/hermes-agent

Silent memory config conflicts and migration gaps

Cluster 124038 · agent. Data as of 2026-10-26 12:29 UTC

1 open item. Fix merged in #131269 on 2 Oct 2026. Check it covers your case.

open issue

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 0 issues already closed.
Fix event: A fix was merged to main in PR #131269. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: 1 issue and 0 PRs.

Next step: read #131269, then check whether your report is the one still open.

Read #131269 Pick up a Lab task

These items address cases where memory-related configuration is silently ignored or lost, and where migration documentation may mislead users about which config keys remain valid.

Open issues1

Issue#124038Same-named setting exists in two config sources with no warning — `config.yaml` `memory.hindsight.mode` is silently ignored

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#131269 fix(memory): never lose memory silently when a provider moves out of core

merged to main

files: agent/agent_init.py, agent/status_output.py, agent/turn_context.py, hermes_cli/memory_provider_migration.py, hermes_cli/plugins_cmd_install.py, hermes_cli/plugins_transaction.py, tests/agent/test_memory_migration_notifications.py, tests/hermes_cli/test_memory_provider_migration.py, website/docs/user-guide/features/memory-providers.md

1 PR closed without merging

From the close comments: merged via another change 1

#125067 fix(memory): migration note must not imply config.yaml provider keys still apply (fixes #124038) · merged via another change → 0cdba5e, #131269, #124038

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem: agent
Merged PRs: #131269
Closed issues: 0
Attempts: 1 PR closed without merging
Fix link checked: 2 Oct 2026

For your agent

The same facts, typed.

cluster/124038.json
cluster/124038.md