# NousResearch/hermes-agent · Slack thread parent message_changed replay bug fix

## Open now

- 1 issue, 2 PRs open on GitHub.
- #118349: \[Bug\]: Slack thread-parent message_changed (reply metadata update) is replayed as a new user turn after gateway restart
- PR #118365: fix(slack): ignore thread parent metadata updates
- PR #123873: fix(slack): message_changed no longer replays an already-answered message after a restart or claim eviction

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.

## TL;DR

- 4 member(s): 1 open issue(s), 0 closed issue(s), 2 open PR(s), 0 merged PR(s), 1 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.50`: the share of member 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.

## Open related issues

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

## Prior & competing PRs

- **#118365: fix(slack): ignore thread parent metadata updates**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#118349`
  - files: `plugins/platforms/slack/adapter.py`, `tests/gateway/test_slack_unfurl_duplicate_turn.py`
- **#123873: fix(slack): message_changed no longer replays an already-answered message after a restart or claim eviction**. open
  - maintainer direction: category `silent_close`; implication `active`
  - files: `plugins/platforms/slack/adapter.py`, `tests/gateway/test_slack_changed_message_restart.py`
- **#123994: fix: resolve #118349 — \[Bug\]: Slack thread-parent message_changed (reply metadata update) is replayed as a new user turn after gateway restart**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`