NousResearch/hermes-agent

Bot mode peer DM fails without profile pin

Cluster 93935. 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.

A bug where peer DM delivery in bot mode omits the profile flag, causing registry resolution to fail when the sending profile is not the default. The items cover the bug report and two related fixes targeting profile pinning in peer DM calls.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 1 · other 1

  • #93952 fix(bot-mode): pin the registry-owning profile on peer DM deliveries · other → d4cec15, #93935
  • #99463 fix(bot-mode): pin default profile for peer dm so the peer registry resolves from non-default profiles · duplicate → #93952
Closed issues · 1
  • Closed#93935Bot Mode: message_agent peer delivery fails from non-default profiles — runner calls 'hermes peer dm' without -p, peer registry is profile-scoped
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

Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.