Cairn
NousResearch/hermes-agent

Hermes update breaks node_modules dependency state

Cluster 34312 · 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, 1 issue 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 0 PRs.

These items concern a recurring issue where the hermes update process leaves web/node_modules in a broken or inconsistent state, causing missing packages and service failures. Fixes and robustness improvements around cleaning and retrying node_modules on dependency layout mismatches are the shared theme.

Open issues1

  • Issue#34335Optimization: Robust update process for hermes update

Open PRs0

No open pull requests.

1 PR closed without merging

From the close comments: done elsewhere 1

  • #34373 fix(update): clean retry web/node_modules on dep-layout mismatch (#34312, #34335) · done elsewhere → 34eb1aa
Closed issues · 1
  • Closed#34312[Bug]: hermes update leaves web/node_modules in broken state — dashboard service crash-loops with lucide-react resolve + missing tsc
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.79: 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
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/34312.json
cluster/34312.md