Cairn
NousResearch/hermes-agent

Slack peer-agent routing tests and reply-storm fixes

Cluster 51630 · gateway. Data as of

Nothing open on GitHub. Fix merged in #69483 on 23 Jul 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 #69483. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items add repeatable smoke tests for Slack peer-agent routing and introduce fixes to prevent multi-agent reply storms, including peer-bot gating, edited-mention handling, and per-channel overrides.

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.

  • #69483 fix(slack): prevent multi-agent reply storms — peer-bot gating, edited mentions, per-channel overrides

    merged to main

    files: contributors/emails/[email protected], contributors/emails/[redacted:email], contributors/emails/[redacted:email], contributors/emails/[redacted:email], contributors/emails/[redacted:email], hermes_cli/config.py, plugins/platforms/mattermost/adapter.py, plugins/platforms/slack/adapter.py, plugins/platforms/slack/plugin.yaml, tests/conftest.py, tests/gateway/test_mattermost.py, tests/gateway/test_slack.py, tests/gateway/test_slack_ignore_other_user_mentions.py, tests/gateway/test_slack_mention.py, tests/gateway/test_slack_peer_agent_smoke.py, tests/gateway/test_slack_require_mention_channels.py, tests/test_slack_thread_require_mention.py, website/docs/user-guide/messaging/slack.md

1 PR closed without merging

From the close comments: merged via another change 1

  • #51637 test(slack): add peer-agent smoke target · merged via another change → #69483, #51630
Closed issues · 1
  • Closed#51630Add repeatable Slack peer-agent routing smoke test
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
#69483
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
23 Jul 2026

For your agent

The same facts, typed.

cluster/51630.json
cluster/51630.md