NousResearch/hermes-agent

Buzz adapter @mention lookup and reply dispatch fixes

Cluster 78797 · gateway. Data as of

Nothing open on GitHub. Fix merged in #99431 on 31 Aug 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #99431. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #99431. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address bugs in the Buzz adapter where @mention tokens were not being looked up to public keys, causing agent-to-agent pings to encounter errors and replies with unresolvable mentions to be silently dropped. Related fixes also cover forum channel dispatch and agent wake behavior on /approve replies.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #99431 fix(buzz): forum channels dispatch, /approve replies wake the agent, and bare names don't (salvages #90314 #75953 #92781 #89751 #82646 #83414)

    merged to main

    files: contributors/emails/[redacted:email], contributors/emails/[redacted:email], plugins/platforms/buzz/adapter.py, tests/gateway/test_buzz_adapter.py, tests/gateway/test_buzz_forum_kinds.py, tests/gateway/test_buzz_mention_resolution.py, tests/tools/test_send_message_target_parse.py, tools/send_message_tool.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #79477 fix(buzz): recover replies with unresolved mentions · done elsewhere → fc0a10a, #99431
  • #83414 fix(buzz): resolve @mentions to pubkeys so agent-to-agent pings work · merged via another change → #99431, #82646, #78797
Closed issues · 1
  • Closed#78797[Bug]: Buzz adapter silently drops replies containing an unresolvable @token (no --mention passed)
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
gateway
Merged PRs
#99431
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
31 Aug 2026

For your agent

The same facts, typed.