Cairn
NousResearch/hermes-agent

Slack thread context missing bot messages on startup

Cluster 38861 · gateway. Data as of

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

These issues and fixes address bot messages being excluded from thread context during cold-start, restart, and rehydration scenarios. The work covers both inbound bot replies being dropped and the lifecycle handling of thread context initialization.

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.

  • #69320 fix(slack): thread-context lifecycle — cold-start, restart rehydration, mention refresh, reply-wake

    merged to main

    files: contributors/emails/[email protected], contributors/emails/[email protected], contributors/emails/[email protected], contributors/emails/[redacted:email], gateway/run.py, gateway/session.py, plugins/platforms/slack/adapter.py, tests/gateway/test_session.py, tests/gateway/test_shared_group_sender_prefix.py, tests/gateway/test_slack.py, tests/gateway/test_slack_approval_buttons.py, tests/gateway/test_slack_mention_humanization.py, tests/gateway/test_slack_wake_external_bot_messages.py

2 PRs closed without merging

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

  • #38936 fix(slack): include bot's own prior replies in cold-start thread context · merged via another change → #69320
  • #39027 fix(slack): bot messages in active threads silently dropped with allow_bots=all · done elsewhere → d3c8667, #30091
Closed issues · 1
  • Closed#38861[Slack] Bot replies excluded from thread context on cold-start sessions
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
#69320
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
22 Jul 2026

For your agent

The same facts, typed.

cluster/38861.json
cluster/38861.md