Cairn
NousResearch/hermes-agent

Buzz adapter thread reply behavior and configuration

Cluster 75082 · gateway. Data as of

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

The short answer

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

These issues and PRs concern the Buzz adapter incorrectly threading replies and ignoring reply configuration options. The work addresses honoring reply_to_mode settings, joining existing threads correctly, and fixing related streaming edit behavior.

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.

  • #99429 fix(buzz): replies join the existing thread, threading is configurable, and streaming edits work (salvages #77080 #79578 #80120 #85613 #86232 #89868)

    merged to main

    files: contributors/emails/[redacted:email], contributors/emails/[redacted:email], contributors/emails/[redacted:email], contributors/emails/[email protected], gateway/display_config.py, gateway/run.py, gateway/stream_consumer.py, plugins/platforms/buzz/adapter.py, plugins/platforms/buzz/plugin.yaml, tests/gateway/test_buzz_adapter.py, tests/gateway/test_buzz_progress_thread_routing.py, tests/gateway/test_buzz_thread_topology.py, tests/gateway/test_run_progress_topics.py, website/docs/user-guide/messaging/buzz.md

1 PR closed without merging

From the close comments: merged via another change 1

  • #85613 Buzz adapter: honor reply_to_mode instead of always threading replies · merged via another change → #99429, #75082, #95842
Closed issues · 1
  • Closed#75082Buzz: a top-level channel mention is answered in a thread, not inline — adapter ignores reply_in_thread
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
gateway
Merged PRs
#99429
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
31 Aug 2026

For your agent

The same facts, typed.

cluster/75082.json
cluster/75082.md