Cairn
NousResearch/hermes-agent

Telegram rich messages and email entity detection handling

Cluster 68754 · gateway. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These three items appear to relate to Telegram rich messages containing email addresses, including a bug report about provider-prefixed email text being rejected and two fixes that skip or auto-enable skipping of entity detection for emails. The titles alone do not show the exact cause or current status.

Open issues1

  • Issue#68754[Bug]: Telegram rich messages can reject provider-prefixed email text

Open PRs2

  • PR#68757fix(telegram): skip rich entity detection for emails
  • PR#68852fix(gateway): auto-enable skip_entity_detection for email-bearing rich messages
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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/68754.json
cluster/68754.md