# NousResearch/hermes-agent · Kanban notify-subscribe missing thread-id handling

## Open now

- 1 issue, 0 PRs open on GitHub.
- #87281: \[Bug\]: kanban notify-subscribe without --thread-id silently delivers pings to the Telegram DM root

These items address a bug where running notify-subscribe without --thread-id silently sends pings to the Telegram DM root instead of warning the user or inheriting a thread ID. The fix adds a warning or inheritance behavior for that missing argument.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 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.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.

## Open related issues

- #87281: \[Bug\]: kanban notify-subscribe without --thread-id silently delivers pings to the Telegram DM root

## Prior & competing PRs

- **#87342: fix(kanban): warn or inherit thread_id on notify-subscribe without --thread-id**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`
- **#125669: fix(kanban): inherit or warn on notify-subscribe without --thread-id (Closes #87281)**. closed without merge
  - maintainer direction: category `wontfix_bydesign`; implication `wontfix`

## Fix status

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