NousResearch/hermes-agent

Bot mode runtime and dependency fixes

Cluster 122490 · environments. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue 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
Nothing open on GitHub.

These items address bot-to-bot messaging failures, delivery runner environment issues (missing third-party dependencies), and startup dependency verification during updates. The work spans launcher spawning, admission error classification, and dependency repair logic.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #123052 fix(update): verify and repair startup dependencies before marking update complete (#122697) · other → #122697, #128992
  • #125865 fix(bot-mode): spawn the delivery runner through the install launcher; classify admission crashes honestly · done elsewhere → #125926, #125308, #123070, #122945
Closed issues · 1
  • Closed#122490[Bug]: bot-to-bot DM delivery runner inherits store python with no third-party deps (ruamel death)
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
environments
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.