NousResearch/hermes-agent

Silent memory loss on provider migration at startup

Cluster 119769. Data as of 2026-10-27 11:58 UTC

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

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue 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 resolved, deciding PR #131269. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #131269, then check it covers your case.

Read #131269 Pick up a Lab task

These items address a scenario where a memory provider migration at agent startup only logs to agent.log, causing silent data loss when allow_lazy_installs is false. The proposed fixes aim to surface migration outcomes through a warning sink so users are notified.

Open issues0

No open issues.

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

#119775 fix(memory): surface startup migration outcomes through warning sink · merged via another change → 0cdba5e, #131269

Closed issues · 1

Closed#119769Memory-provider migration outcome at agent start is agent.log-only; with allow_lazy_installs: false the user loses memory silently

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

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

For your agent

The same facts, typed.

cluster/119769.json
cluster/119769.md