Cairn
NousResearch/hermes-agent

Telegram message content edge-case fixes

Cluster 60848 · gateway. 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.

These items address two distinct Telegram message-handling edge cases: filtering out visually empty messages containing zero-width or invisible characters, and preserving newlines in rich slash-command output.

Open issues1

  • Issue#60848bug(telegram): empty-message guard misses zero-width/invisible characters — visually empty bubbles delivered

Open PRs1

  • PR#60865fix(telegram): reject zero-width/invisible-only messages in empty-send guard (#60848)

1 PR closed without merging

From the close comments: merged via another change 1

  • #46129 fix(telegram): preserve newlines in rich slash-command output (#46070) · merged via another change → #50196
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
gateway
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/60848.json
cluster/60848.md