Cairn
NousResearch/hermes-agent

Slack assistant thread status not cleared after replies

Cluster 8387. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 4 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

Most members (four of five) concern clearing the Slack assistant thread status or typing indicator after a response is delivered, including one report involving MCP tools running post-reply. One member is about respecting reply_in_thread and reply_to_mode for channel replies, which appears to be a separate topic.

Open issues0

No open issues.

Open PRs0

No open pull requests.

4 PRs closed without merging

From the close comments: done elsewhere 2 · closed without comment 1 · other 1

  • #8413 fix(slack): clear assistant thread status after reply · done elsewhere → 70a3370
  • #8414 fix(slack): clear assistant typing indicator after response delivery · closed without comment
  • #8598 fix(slack): respect reply_in_thread and reply_to_mode for channel replies · other → #17184, #16188
  • #12901 fix(slack): explicitly clear assistant thread status · done elsewhere → 70a3370
Closed issues · 1
  • Closed#8387Slack: assistant.threads.setStatus persists after response when MCP tools execute post-reply
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.40: 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

Closed issues
1
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/8387.json
cluster/8387.md