Cairn
NousResearch/hermes-agent

Sanitize Telegram reply context Markdown injection

Cluster 69060 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

These items address a bug where inbound Telegram reply-to context was injecting raw, truncated Markdown into user messages via the gateway. The fix involves stripping Markdown before that content is injected.

Open issues0

No open issues.

Open PRs2

  • PR#69087fix(gateway): sanitize reply-to context by stripping Markdown before injection (#69060)
  • PR#69101fix(gateway): sanitize reply context excerpts
Closed issues · 1
  • Closed#69060Telegram inbound reply context injects truncated raw Markdown into the user message
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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/69060.json
cluster/69060.md