Cairn
NousResearch/hermes-agent

Telegram tables flattened to bullets in final rich messages

Cluster 45323 · gateway. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
10items grouped
Known?
Yes. 10 related items grouped here, 4 issues already closed.
Fix event
No fix has been merged to main. 3 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 2 PRs.

Members mostly concern Telegram messages where a streaming draft or preview shows a table, but the final send reportedly falls back to MarkdownV2 or converts pipe tables to bullet lists. Several are issue reports and several are proposed fixes touching rich-message sends, expect_edits handling, and table formatting, though the exact cause is described differently across them.

Open issues1

  • Issue#46515Telegram: sendRichMessageDraft works but final message falls back to MarkdownV2 (expect_edits kills rich path)

Open PRs2

  • PR#45327fix(telegram): preserve pipe tables on rich-message and standalone send paths
  • PR#46536fix(gateway): omit expect_edits on finalize so Telegram uses sendRichMessage

3 PRs closed without merging

From the close comments: closed without comment 1 · superseded by another PR 1 · other 1

  • #45387 fix(gateway): preserve tables in rich Telegram sends and send_message (#45323) · superseded by another PR → #45327, #45323
  • #49850 fix(telegram): replace table-to-bullet conversion with monospaced code block · closed without comment
  • #62715 fix: ensure rich messages are used for final messages when notify=true (#49137) · other
Closed issues · 4
  • Closed#45323[Bug]: Telegram rich tables are rewritten into bullets by the shared formatter
  • Closed#46540[Bug]: Draft streaming — final message falls back to MarkdownV2 instead of Rich Message
  • Closed#49137rich_messages: true - streaming preview shows table but final sendMessage falls back to bullet list
  • Closed#49452[Telegram] Markdown pipe tables converted to bullet lists in streaming finalization
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.15: 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
gateway
Closed issues
4
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/45323.json
cluster/45323.md