Memory provider config reading from config.yaml fixes
NousResearch/hermes-agent · cluster 62540 · agent
Data as of
Nothing open on GitHub. Fix merged in #77747. Check it covers your case.
The short answer
- Known?
- Yes. 6 related items grouped here, 2 issues already closed.
- Fix event
- A fix was merged to main in PR #77747. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #77747. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where OpenViking and RetainDB memory providers could not be configured via config.yaml or the Dashboard, requiring environment variables instead. Related work also covers lifecycle hardening and endpoint safety for the OpenViking plugin.
Open issues0
Open PRs0
Fixes on record
-
#77747 fix(openviking): harden lifecycle, endpoint safety, and dashboard config
files:
agent/memory_provider.py,contributors/emails/[redacted:email],contributors/emails/[redacted:email],hermes_cli/web_server.py,plugins/memory/openviking/README.md,plugins/memory/openviking/__init__.py,plugins/memory/retaindb/__init__.py,tests/hermes_cli/test_web_server.py,tests/openviking_plugin/test_openviking.py,tests/plugins/memory/test_openviking_endpoint_always_blocked.py,tests/plugins/memory/test_openviking_provider.py,tests/plugins/memory/test_retaindb_provider.py,web/src/lib/api.ts,web/src/pages/PluginsPage.tsx
3 PRs closed without merging
From the close comments: merged via another change 3
-
#62541 fix(openviking): read recall settings from config.yaml first, env vars as fallback · merged via another change →
#77747 -
#68228 fix(memory): read non-secret provider config from config.yaml for OpenViking and RetainDB (#68209) · merged via another change →
#77747 -
#76782 fix(openviking): harden lifecycle, endpoint safety, and dashboard config · merged via another change →
#77747,#76782
Closed issues · 2
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.49: 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
- #77747
- Closed issues
- 2
- Attempts
- 3 PRs closed without merging
- Fix link checked
- 3 Aug 2026