Cairn

Slack thread parent message_changed replay bug fix

NousResearch/hermes-agent · cluster 118349 · gateway

Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These items address a bug where Slack's thread-parent metadata update events (message_changed) are incorrectly replayed as new user turns after a gateway restart or claim eviction. The group covers the bug report and multiple related fix attempts targeting the same issue.

Open issues1

  • Issue#118349[Bug]: Slack thread-parent message_changed (reply metadata update) is replayed as a new user turn after gateway restart

Open PRs2

  • PR#118365fix(slack): ignore thread parent metadata updates
  • PR#123873fix(slack): message_changed no longer replays an already-answered message after a restart or claim eviction

1 PR closed without merging

From the close comments: other 1

  • #123994 fix: resolve #118349 — [Bug]: Slack thread-parent message_changed (reply metadata update) is replayed as a new user turn after gateway restart · other
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
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/118349.json
cluster/118349.md