Cairn
NousResearch/hermes-agent

Auto-start OpenViking server on health check failure

Cluster 39981 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs address the OpenViking memory provider not automatically starting its server, requiring users to launch it manually. The work involves triggering an auto-start when a health check fails.

Open issues0

No open issues.

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: closed without comment 3

  • #39998 fix(memory): auto-start local OpenViking server · closed without comment
  • #40013 feat(openviking): auto-start server when health check fails · closed without comment
  • #40057 fix(openviking): auto-start openviking-server when health check fails · closed without comment
Closed issues · 1
  • Closed#39981OpenViking memory provider doesn't auto-start — you have to run `openviking-server` by hand
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.50: 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

Subsystem
agent
Closed issues
1
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/39981.json
cluster/39981.md