Preserving memory provider when plugin manager evicts plugins
Cluster 129198 · agent. Data as of
Nothing open on GitHub. Fix merged in #144257 on 25 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #144257. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #144257. That is separate from the fix event. - Still open
- Nothing open on GitHub.
The members concern the plugin manager (pm) and the memory provider setting: one issue reports that pm sync clears memory.provider when evicting a plugin after a dependency fetch fails on a TLS error, and a related fix title and an update title describe keeping the provider during eviction or plugin disabling. The titles suggest a shared theme, but their status and outcomes are not stated.
Open issues0
Open PRs0
Fixes on record
-
#144257 An update that turns a plugin off keeps your memory provider and turns the plugin back on once it fits (#131216, #129198, #125919)
files:
agent/agent_init.py,agent/agent_init_memory_provider.py,agent/reasoning_params.py,contributors/emails/[redacted:email],hermes_cli/config_defaults.py,hermes_cli/doctor.py,hermes_cli/doctor_state.py,hermes_cli/memory_setup.py,hermes_cli/plugins_admission.py,hermes_cli/plugins_cmd.py,hermes_cli/web_server_memory.py,plugins/memory/__init__.py,pm/plugin_eviction.py,pm/plugins_state.py,pm/publication.py,pm/workspace.py,tests/agent/test_config_load_warning.py,tests/agent/test_memory_provider_unavailable_warning.py,tests/pm/test_plugin_survival_contract.py,website/docs/getting-started/updating.md
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#129201 fix(pm): preserve explicit memory provider during plugin eviction · superseded by another PR →
1d258cc,#144257
Closed issues · 1
- Closed#129198[Bug]: pm sync silently clears memory.provider when it evicts a plugin whose dependency fetch failed on a host TLS error
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.00means 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 LabAt a glance
- Subsystem
- agent
- Merged PRs
- #144257
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 25 Oct 2026