{"repo":"NousResearch/hermes-agent","public_id":"118349","display_label":"Slack thread parent message_changed replay bug fix","summary":"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.","subsystem":"gateway","counts":{"members":4,"open_issues":1,"open_issues_distinct":1,"open_prs":2,"closed_issues":0,"merged_prs":0,"attempt_prs":3},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.5},"fix_edges":[],"members":[{"kind":"issue","number":118349,"title":"[Bug]: Slack thread-parent message_changed (reply metadata update) is replayed as a new user turn after gateway restart","url":null,"state":"open"},{"kind":"pr","number":118365,"title":"fix(slack): ignore thread parent metadata updates","url":null,"state":"open","close_reason":{"refs":[{"kind":"pr","value":"#118349","number":118349}],"category":"uncategorized","implication":"needs_llm"},"merged":false},{"kind":"pr","number":123873,"title":"fix(slack): message_changed no longer replays an already-answered message after a restart or claim eviction","url":null,"state":"open","close_reason":{"category":"silent_close","implication":"active"},"merged":false},{"kind":"pr","number":123994,"title":"fix: resolve #118349 — [Bug]: Slack thread-parent message_changed (reply metadata update) is replayed as a new user turn after gateway restart","url":null,"state":"closed","close_reason":{"category":"silent_close","implication":"active"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}