OpenViking URI format migration and canonicalization
Cluster 91995 · agent. Data as of
Nothing open on GitHub. Fix merged in #94515 on 25 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #94515. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #94515. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug was identified where the plugin used a URI scheme removed upstream, and related fixes address migrating to the canonical viking://~ home alias format. Multiple fix attempts or iterations appear to be represented.
Open issues0
Open PRs0
Fixes on record
-
#94515 fix(memory): emit canonical OpenViking user URIs
files:
plugins/memory/openviking/README.md,plugins/memory/openviking/__init__.py,tests/openviking_plugin/test_openviking.py,tests/plugins/memory/test_openviking_provider.py
2 PRs closed without merging
From the close comments: merged via another change 2
Closed issues · 1
- Closed#91995[Bug] OpenViking plugin uses uid-less viking://user/<segment> URIs that upstream removed in #4196 — will 400 on next OV release
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.00means 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 LabAt a glance
- Subsystem
- agent
- Merged PRs
- #94515
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 25 Aug 2026