Cairn
NousResearch/hermes-agent

Admin-owned tool entries cause permission errors on Windows

Cluster 126860 · hermes cli. Data as of

1 open item. Fix attempted, not merged.

The short answer

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

A bug on Windows where elevated installs leave tool store entries owned by an administrator account, causing permission errors for later non-elevated runs. Includes a diagnostic flag and a repair mechanism for affected entries.

Open issues1

  • Issue#126860[Bug]: Windows — an elevated install/update leaves %LOCALAPPDATA%\hermes\tools entries admin-owned; later non-elevated `hermes update` dies with WinError 5

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: closed without comment 1 · other 1

  • #127597 fix(pm): detect and repair admin-owned tool entries published from elevated sessions · other
  • #132699 fix(doctor): flag admin-owned tools store entries on Windows (fixes #126860) · closed without comment
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.67: 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
hermes cli
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/126860.json
cluster/126860.md