Memory provider workers context and secret binding
Cluster 108995. Data as of
Nothing open on GitHub. Fix merged in #109563 on 13 Sep 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 #109563. 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
- Nothing open on GitHub.
These items address a bug where OpenViking background worker threads start without the correct context, causing secret resolution failures and broken memory writes under multiplexed profiles. The work involves refactoring memory providers to spawn context-bound threads and surface secret errors loudly.
Open issues0
Open PRs0
Fixes on record
-
#109563 refactor(plugins): memory providers spawn context-bound threads and use core config/JSON writers; secret shims fail loud; HERMES_HOME and model-provider thinking/fetch_models copies collapse
files:
agent/azure_identity_adapter.py,agent/memory_manager.py,agent/memory_provider.py,agent/reasoning_effort.py,hermes_cli/models.py,plugins/memory/byterover/__init__.py,plugins/memory/hindsight/__init__.py,plugins/memory/holographic/__init__.py,plugins/memory/honcho/__init__.py,plugins/memory/honcho/cli.py,plugins/memory/honcho/client.py,plugins/memory/honcho/dialectic.py,plugins/memory/honcho/oauth.py,plugins/memory/honcho/recall_sync.py,plugins/memory/honcho/session.py,plugins/memory/mem0/__init__.py,plugins/memory/mem0/_oss_providers.py,plugins/memory/mem0/_setup.py,plugins/memory/openviking/__init__.py,plugins/memory/retaindb/__init__.py(+32 more)
1 PR closed without merging
From the close comments: done elsewhere 1
-
#108996 fix(memory/openviking): run background workers in the spawner's context · done elsewhere →
#109563
Closed issues · 1
- Closed#108995[Bug]: OpenViking background workers start with an empty Context, so a multiplexed secondary profile's memory writes die on UnscopedSecretError
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
- Merged PRs
- #109563
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 13 Sep 2026