Cairn
NousResearch/hermes-agent

OpenViking plugin auth, headers, and API fixes

Cluster 21130 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 3 issues 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 multiple interrelated problems in the OpenViking plugin: incorrect API endpoint paths, broken authentication header behavior with API key auth, tenant-scoping header mismatches causing memory search failures, and compatibility issues with OpenViking v0.4.1+.

Open issues0

No open issues.

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1 · won't fix / by design 1

  • #21136 fix(openviking): resolve 403 with API key auth and late .env loading · done elsewhere → #51952, #21130
  • #47355 fix(openviking): skip tenant headers when api_key is set · duplicate → 4af16b5, #48206
  • #47528 fix(openviking): v0.4.1 compatibility - auth headers and search limit · won't fix / by design → #47527, #46532, #47528
Closed issues · 3
  • Closed#21130OpenViking plugin: 403 with API key auth + env vars not reloaded after /reload
  • Closed#47344OpenViking plugin always sends X-OpenViking-Account header, broken on OV v0.4.1+ with api_key auth
  • Closed#47527fix(openviking): v0.4.1 compatibility - auth headers and search limit
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.25: 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
3
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/21130.json
cluster/21130.md