Cairn
NousResearch/hermes-agent

Slack bot message handling and thread routing fixes

Cluster 30091 · gateway. Data as of

Nothing open on GitHub. Fix merged in #70192 on 23 Jul 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 #70192. 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 address cases where bot-to-bot or workflow messages in Slack threads are silently dropped despite allow_bots=all being configured. The work involves authorization ordering, thread-parent context, multi-workspace cache keys, Slack Connect file handling, and diagnostic surfacing for bot-event and allow_bots interop issues.

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.

  • #70192 fix(slack): quiet logs — catch-all ack, no content leaks, throttled warnings

    merged to main

    files: contributors/emails/[redacted:email], contributors/emails/[redacted:email], gateway/channel_directory.py, gateway/display_config.py, plugins/platforms/slack/adapter.py, tests/gateway/test_channel_directory.py, tests/gateway/test_display_config.py, tests/gateway/test_restart_notification.py, tests/gateway/test_slack.py, tests/gateway/test_slack_log_noise.py, tests/gateway/test_slack_mention.py

2 PRs closed without merging

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

  • #30185 fix(slack): surface bot-event arrival and allow_bots interop diagnostics · merged via another change → #70192
  • #39027 fix(slack): bot messages in active threads silently dropped with allow_bots=all · done elsewhere → d3c8667, #30091
Closed issues · 1
  • Closed#30091Slack: bot-to-bot messages in shared threads silently dropped even with allow_bots=all
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
#70192
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
23 Jul 2026

For your agent

The same facts, typed.

cluster/30091.json
cluster/30091.md