Cairn
NousResearch/hermes-agent

Telegram rich_messages table formatting conflict fix

Cluster 118047 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

A bug where conflicting platform hints caused Telegram to both forbid and allow tables when rich_messages is enabled. The fixes swap the base hint for a rich variant and remove the no-tables steering when rich_messages is on.

Open issues1

  • Issue#118047[Bug]: Telegram base platform hint forbids tables while the rich_messages hint instructs the model to use them

Open PRs1

  • PR#118068fix(telegram): swap the base platform hint for a rich variant when rich_messages is on

1 PR closed without merging

From the close comments: stale or abandoned 1

  • #118064 fix(agent): drop Telegram no-tables steering when rich_messages is on · stale or abandoned
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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/118047.json
cluster/118047.md