NousResearch/hermes-agent

Telegram streaming flood pacing and word-boundary fixes

Cluster 116312. Data as of 2026-10-24 13:18 UTC

Nothing open on GitHub. Fix merged in #116987 on 20 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #116987. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #116987. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #116987, then check it covers your case.

Read #116987 Pick up a Lab task

These items address unpaced Telegram streaming edits causing flood penalties, proposing a shared send-and-edit rate-limit budget per chat and word-boundary-aware continuation when messages must be cut.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#116987 fix(telegram): streaming previews stop earning flood penalties — shared send+edit slot, retry_after honoured, word-boundary continuation (#116312, salvage #116385)

merged to main

files: contributors/emails/[redacted:email], gateway/stream_consumer.py, gateway/stream_consumer_fallback.py, gateway/stream_consumer_transport.py, plugins/platforms/telegram/adapter.py, tests/gateway/test_stream_consumer_continuation_cut.py, tests/gateway/test_stream_edit_flood_retry_after.py, tests/gateway/test_telegram_shared_outbound_budget.py, tests/gateway/test_telegram_typing_retrigger.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

#116339 fix(gateway): pace Telegram streaming sends and edits on one shared budget; word-boundary fallback cut · done elsewhere → a57a5f9, #116987, #116312, #116385
#116385 fix(telegram): shared per-chat send+edit pacing budget and word-boundary continuation cut · merged via another change → a57a5f9, #116987, #116312, #116385

Closed issues · 1

Closed#116312[Bug]: Telegram streaming edits are unpaced — 83% of flood penalties come from them, and the fallback continuation then cuts mid-word

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

Merged PRs: #116987
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 20 Sep 2026

For your agent

The same facts, typed.

cluster/116312.json
cluster/116312.md