Cairn
NousResearch/hermes-agent

openviking server lifecycle and stability fixes

Cluster 74846. Data as of

Nothing open on GitHub. Fix merged in #77747 on 3 Aug 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue 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.

Multiple fixes targeting the openviking component, addressing duplicate server spawning on occupied ports, a missing cooldown causing repeated spawn loops, and general hardening of lifecycle management and endpoint safety.

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.

  • #77747 fix(openviking): harden lifecycle, endpoint safety, and dashboard config

    merged to main

    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

2 PRs closed without merging

From the close comments: merged via another change 2

  • #74959 fix(openviking): don't spawn a second server onto a live port (#74846) · merged via another change → #77747
  • #76782 fix(openviking): harden lifecycle, endpoint safety, and dashboard config · merged via another change → #77747, #76782
Closed issues · 1
  • Closed#74846fix(openviking): missing cooldown on unreachable health state causes spawn loop (DataDirectoryLocked every 2-5 min)
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
#77747
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
3 Aug 2026

For your agent

The same facts, typed.

cluster/74846.json
cluster/74846.md