Cairn
NousResearch/hermes-agent

uv sync behavior fixes during hermes updates

Cluster 8744 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 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 1 PR.

These members address issues with how uv dependencies are synchronized when updating or running hermes, including unnecessary re-resolution on every launch and ensuring locked installs are used when a lockfile exists.

Open issues1

  • Issue#8744[Bug] uv run hermes resolves dependencies on every launch — requires internet post-update

Open PRs1

  • PR#14835fix(cli): use uv sync --locked when uv.lock exists during update

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #8757 fix(update): sync uv-managed installs during hermes update · superseded by another PR → #14835
  • #125790 fix(update): reconcile venv with uv.lock so uv run hermes stops re-resolving (#8744) · done elsewhere
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.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/8744.json
cluster/8744.md