# NousResearch/hermes-agent · Telegram image cache stale content bug and fixes

## Open now

- Nothing open on GitHub.

A bug where the Telegram integration writes stale image content to new cache filenames, with related fixes addressing content-hash naming and retry logic for stale photo downloads from the Bot API.

## TL;DR

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

## Closed / duplicate issues

- #35242: \[Bug\]: Telegram image_cache writes stale content from previous image to new filename

## Prior & competing PRs

- **#35260: fix(gateway): use content-hash filename in cache_image_from_bytes**. closed without merge
  - maintainer direction: category `wontfix_bydesign`; implication `wontfix`; refs `#35242`
- **#35263: fix(telegram): detect and retry stale photo downloads from Bot API (#35242)**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#35242`

## Fix status

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