Cairn
NousResearch/hermes-agent

Slack thread reply wake and state persistence fixes

Cluster 63530 · 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
3items grouped
Known?
Yes. 3 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 unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These members address two related Slack agent issues: the agent failing to wake when humans reply in threads, and reply-tracking state being lost on restart. Both the bug report and fixes target thread reply detection and persistence 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.

  • #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

1 PR closed without merging

From the close comments: merged via another change 1

  • #64067 fix(slack): wake on human replies in threads whose root we authored (#63530) · merged via another change → #69320, #63530
Closed issues · 1
  • Closed#63530[Slack] Replies to bot messages posted outside gateway send() never wake the agent; reply-tracking state is also lost on restart
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
#69320
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
22 Jul 2026

For your agent

The same facts, typed.

cluster/63530.json
cluster/63530.md