Slack bot-to-bot messaging documentation
NousResearch/hermes-agent · cluster 26184 · docs
Data as of
Nothing open on GitHub. Fix merged in #69483. Check it covers your case.
The short answer
- Known?
- Yes. 6 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
resolved, deciding PR #70198. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items all concern documenting the SLACK_ALLOW_BOTS / allow_bots configuration option and related bot message handling behavior for Slack. The work spans multiple documentation efforts covering multi-agent and bot-to-bot messaging scenarios.
Open issues0
Open PRs0
Fixes on record
-
#69483 fix(slack): prevent multi-agent reply storms — peer-bot gating, edited mentions, per-channel overrides
files:
contributors/emails/[redacted:email],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 -
#70198 docs(slack): allow_bots, command handling, and wave 1-3 feature documentation
files:
contributors/emails/[redacted:email],website/docs/reference/environment-variables.md,website/docs/reference/slash-commands.md,website/docs/user-guide/messaging/slack.md
3 PRs closed without merging
From the close comments: merged via another change 1 · stale or abandoned 1 · other 1
Closed issues · 1
- Closed#26184Document SLACK_ALLOW_BOTS / allow_bots config for multi-agent Slack threads
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.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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