OpenViking memory URI path fixes and scoping

NousResearch/hermes-agent · cluster 36969 · agent

Data as of

Nothing open on GitHub. Fix merged in #39002. Check it covers your case.

The short answer

0open issues
0open PRs
11items grouped
Known?
Yes. 11 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #39002. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #39002. That is separate from the fix event.
Still open
Nothing open on GitHub.

Multiple bug reports and fixes addressing incorrect URI paths for Viking memory writes, including removal of a spurious 'peers' segment and efforts to properly scope memory storage per-agent and per-user namespace. One unrelated item concerns a Hermes bridge token security topic.

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.

  • #39002 fix(openviking): scope memory writes per-agent (salvage #37279)

    merged to main

    files: plugins/memory/openviking/__init__.py, scripts/release.py, tests/openviking_plugin/test_openviking.py

8 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1 · superseded by another PR 1 · other 5

  • #37158 fix(openviking): scope memory URIs by agent · other → 4af16b5, #48206
  • #37279 fix(openviking): add missing /agent/{agent}/ segment to memory URI · merged via another change → #39002
  • #50812 fix(openviking): remove incorrect 'peers' segment from memory URI path · other
  • #50826 fix(openviking): remove incorrect 'peers' segment from memory URI path · other
  • #50829 fix(openviking): remove incorrect 'peers' segment from memory URI path · done elsewhere
Show 3 more
  • #51231 fix(openviking): write memories under agent root · other → 05eecbc, #134350
  • #68470 codex/security hermes bridge token · other
  • #83647 fix(openviking): bind identity to the initialized profile · superseded by another PR → 05eecbc, #5374, #4196
Closed issues · 2
  • Closed#36969[Bug]: Bug Report: OpenViking memory writes cross tenant boundaries
  • Closed#50701[Bug] viking_remember writes to wrong URI path (viking://user/peers/ doesn't exist)
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.17: 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
Merged PRs
#39002
Closed issues
2
Attempts
8 PRs closed without merging
Fix link checked
5 Jun 2026

For your agent

The same facts, typed.