# NousResearch/hermes-agent · Slack reminder thread delivery fix for near one-shots

## Open now

- Nothing open on GitHub.

These items concern a bug where Slack reminders created from top-level messages were delivered to the wrong location (channel or bot-opened thread) instead of the originating thread. The work focuses on preserving the correct reply-in-thread context for near one-shot cron reminders.

## 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 #117620. Verify it addresses your case.
- **Recommended:** read PR #117620 (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-117620`. 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

- #117306: Slack: a reminder created from a top-level message is delivered to the channel, not to the thread the bot opened under it

## Prior & competing PRs

- **#117620: fix(cron): near one-shot Slack reminders deliver into the thread they were asked in; expired run_at fails closed (#117306, #117357, salvage #117343)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `tests/cron/test_cron_origin_synthetic_thread.py`, `tools/cronjob_job_args.py`, `tools/cronjob_tools.py`
- **#117343: fix(cron): keep the Slack reply-in-thread origin for near one-shots**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `553600442e`, `#117620`

## Fix status

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