Cairn
NousResearch/hermes-agent

Telegram HTML formatting lost in cron send path

Cluster 124413 · agent. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 0 PRs.

A bug report and related fix attempts address Telegram message delivery silently stripping all formatting when HTML tags are present, with proposed retry logic falling back to MarkdownV2 before plain text.

Open issues1

  • Issue#124413[Bug]: Cron→Telegram deliveries never use Rich Messages and silently lose ALL formatting when any HTML tag is present (standalone send path)

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: partial fix 1 · other 1

  • #124477 fix(tools): retry Telegram HTML rejections as MarkdownV2 before plain text · other → #115014, #46118, #114076
  • #126074 fix(tools): retry Telegram HTML rejections as MarkdownV2 before plain text · partial fix
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item 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.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/124413.json
cluster/124413.md