{"repo":"NousResearch/hermes-agent","public_id":"45323","display_label":"Telegram tables flattened to bullets in final rich messages","summary":"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.","subsystem":"gateway","counts":{"members":10,"open_issues":1,"open_issues_distinct":1,"open_prs":2,"closed_issues":4,"merged_prs":0,"attempt_prs":5},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_PARTIAL","link_density":0.15111111111111108},"fix_edges":[],"members":[{"kind":"issue","number":45323,"title":"[Bug]: Telegram rich tables are rewritten into bullets by the shared formatter","url":null,"state":"closed"},{"kind":"issue","number":46515,"title":"Telegram: sendRichMessageDraft works but final message falls back to MarkdownV2 (expect_edits kills rich path)","url":null,"state":"open"},{"kind":"issue","number":46540,"title":"[Bug]: Draft streaming — final message falls back to MarkdownV2 instead of Rich Message","url":null,"state":"closed"},{"kind":"issue","number":49137,"title":"rich_messages: true - streaming preview shows table but final sendMessage falls back to bullet list","url":null,"state":"closed"},{"kind":"issue","number":49452,"title":"[Telegram] Markdown pipe tables converted to bullet lists in streaming finalization","url":null,"state":"closed"},{"kind":"pr","number":45327,"title":"fix(telegram): preserve pipe tables on rich-message and standalone send paths","url":null,"state":"open","close_reason":{"refs":[{"kind":"commit","value":"5600105478ffde29d7566b45421b100eaa29c4ef","number":0},{"kind":"pr","value":"#45323","number":45323}],"category":"implemented_elsewhere","implication":"superseded"},"merged":false},{"kind":"pr","number":45387,"title":"fix(gateway): preserve tables in rich Telegram sends and send_message (#45323)","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#45327","number":45327},{"kind":"pr","value":"#45323","number":45323}],"category":"superseded_by_pr","implication":"superseded"},"merged":false,"is_fix_pr":true,"fix_tier":"suggested","fix_detail_withheld":true},{"kind":"pr","number":46536,"title":"fix(gateway): omit expect_edits on finalize so Telegram uses sendRichMessage","url":null,"state":"open","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false},{"kind":"pr","number":49850,"title":"fix(telegram): replace table-to-bullet conversion with monospaced code block","url":null,"state":"closed","close_reason":{"category":"silent_close","implication":"active"},"merged":false},{"kind":"pr","number":62715,"title":"fix: ensure rich messages are used for final messages when notify=true (#49137)","url":null,"state":"closed","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}