Cairn
NousResearch/hermes-agent

Slack thread-context refresh on explicit @mention

Cluster 23918 · 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.

The members concern Slack thread-context handling, centered on refreshing context when someone explicitly @mentions the bot in an active thread. One broader pull request also mentions related lifecycle topics (cold-start, restart rehydration, reply-wake). The titles do not indicate the status of any of this work.

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

  • #23927 fix(slack): refresh active thread context on explicit mention · merged via another change → #69320
Closed issues · 1
  • Closed#23918Slack: explicit @mention in active thread should refresh thread context
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/23918.json
cluster/23918.md