Cairn
NousResearch/hermes-agent

OpenViking memory storage and endpoint path changes for viking_remember

Cluster 17998. 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, 1 issue already closed.
Fix event
No fix has been merged to main. 4 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this resolved, deciding PR #30317. That is separate from the fix event.
Still open
Nothing open on GitHub.

Most members concern the openviking integration, especially how viking_remember stores memories (content/write API vs. session messages, extraction pipeline, committing). One bug report describes empty sessions with data not persisted, and one item covers migrating endpoints from /api/v1/ to v0.2.x paths; outcomes are not established here.

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.

  • #30317 fix(openviking): store memories via content/write API instead of session messages

    merged to main

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

4 PRs closed without merging

From the close comments: closed without comment 1 · merged via another change 1 · other 2

  • #18002 fix(openviking): commit explicit remember memories · other → #18320, #17998
  • #18320 fix(openviking): migrate all endpoints from /api/v1/ to v0.2.x paths · other → #17998
  • #29664 fix(openviking): bypass broken extraction pipeline in viking_remember · closed without comment
  • #29733 fix(openviking): store memories via content/write API instead of session messages · merged via another change → #30317, #17998, #29664
Closed issues · 1
  • Closed#17998[Bug]: viking_remember creates empty sessions — data never persisted
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.33: 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
#30317
Closed issues
1
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/17998.json
cluster/17998.md