Cairn
NousResearch/hermes-agent

Isolate managed uv toolchain from user environment

Cluster 101269 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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 1 PR.

These issues and PRs address a problem where the managed uv/uvx installation interferes with or shadows the user's own uv installation. The work focuses on cross-platform isolation of the managed toolchain, including fixes for gaps remaining after a prior migration.

Open issues1

  • Issue#101269[Bug]: Hermes' uv escapes its PM store, shadowing the user's own uv on Windows

Open PRs1

  • PR#124313fix(pm): close the uv-isolation gaps left by the PM migration (#101269)

1 PR closed without merging

From the close comments: duplicate 1

  • #101291 fix(uv): isolate managed uv/uvx toolchain from the user (cross-platform) · duplicate → afcb61a, d205375, e8ab070, db23c79, 4dac5f2, #101269, #21457, #97634, #101291
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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/101269.json
cluster/101269.md