# NousResearch/hermes-agent · Cron parsing of named Telegram DM topic targets

## Open now

- 1 issue, 1 PR open on GitHub.
- #80483: Cron misparses named Telegram private-DM topic targets
- PR #97139: fix(cron): resolve named Telegram DM topics

These items concern a bug where cron misparses named Telegram private-DM topic targets, along with associated fix attempts. The work focuses on parsing and resolving these named targets correctly.

## TL;DR

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

- #80483: Cron misparses named Telegram private-DM topic targets

## Prior & competing PRs

- **#80778: fix(cron): parse and resolve named Telegram private-DM topic targets**. closed without merge
  - maintainer direction: category `stale_abandoned`; implication `active`
- **#97139: fix(cron): resolve named Telegram DM topics**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#80483`
  - files: `cron/scheduler.py`, `tests/cron/test_scheduler.py`, `tests/tools/test_send_message_target_parse.py`, `tools/send_message_tool.py`

## Fix status

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