# NousResearch/hermes-agent · Slack clarify card expiry and timeout handling

## Open now

- Nothing open on GitHub.

These issues and fixes address how Slack clarify cards handle expiration, including proactive expiry, in-place retirement on timeout, and a bug where expiry messaging only appeared after a stale button interaction.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #111410. Verify it addresses your case.
- **Recommended:** read PR #111410 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-111410`. 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.67`: 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.

## Closed / duplicate issues

- #110821: \[Bug\]: Slack clarify cards only show expiry after a stale button is clicked

## Prior & competing PRs

- **#111410: fix(slack): clarify cards retire in place on timeout, reset and free-prose cancel (#110821, #111019, salvage #111027)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `gateway/platforms/base.py`, `gateway/run.py`, `gateway/run_inbound.py`, `gateway/run_turn_runner.py`, `plugins/platforms/slack/adapter.py`, `tests/gateway/test_clarify_card_retire_on_timeout.py`, `tests/gateway/test_clarify_send_timeout_ambiguity.py`, `tests/gateway/test_clarify_thread_followup_not_swallowed.py`, `tests/gateway/test_slack_clarify_buttons.py`, `website/docs/user-guide/messaging/slack.md`
- **#110828: fix(slack): expire clarify cards proactively**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`

## Fix status

- Merged to main in PR #111410 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-15`.