# NousResearch/hermes-agent · Silent memory config conflicts and migration gaps

## Open now

- 1 issue, 0 PRs open on GitHub.
- #124038: Same-named setting exists in two config sources with no warning — \`config.yaml\` \`memory.hindsight.mode\` is silently ignored

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.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #131269. Verify it addresses your case.
- **Recommended:** read PR #131269 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Open related issues

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

## Prior & competing PRs

- **#131269: fix(memory): never lose memory silently when a provider moves out of core**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - 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`
- **#125067: fix(memory): migration note must not imply config.yaml provider keys still apply (fixes #124038)**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `0cdba5ec7e`, `#131269`, `#124038`

## Fix status

- Merged to main in PR #131269 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-10-02`.
- Subsystem: `agent`