Cairn
NousResearch/hermes-agent

Webhook drops Telegram DM-topic routing keys

Cluster 33375 · gateway. Data as of

1 open item. Fix attempted, not merged.

The short answer

0open issues
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue 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
0 issues and 1 PR.

These items concern a bug where the webhook adapter fails to forward Telegram DM-topic routing keys from deliver_extra, causing cross-platform delivery metadata to be incomplete. The group covers the bug report and two related fixes targeting this routing key propagation issue.

Open issues0

No open issues.

Open PRs1

  • PR#33397fix(webhook): surface DM topic routing keys in cross-platform delivery metadata

1 PR closed without merging

From the close comments: stale or abandoned 1

  • #33396 fix(webhook): forward Telegram DM-topic routing keys from deliver_extra · stale or abandoned
Closed issues · 1
  • Closed#33375[Bug] Webhook adapter drops telegram_reply_to_message_id from deliver_extra; all DM-topic webhook deliveries fail
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
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/33375.json
cluster/33375.md