NousResearch/hermes-agent

Duplicate reply bug fix for non-editable platforms

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

Nothing open on GitHub. Fix merged in #117635 on 21 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 #117635. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #117635. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #117635 Pick up a Lab task

These issues and PRs concern a bug where non-editable platforms (such as Weixin) send long replies twice due to an interim callback incorrectly falling back to a plain send when no stream consumer exists. The work addresses preventing duplicate delivery and ensuring interim finals are correctly tracked in the delivery ledger.

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.

#117635 fix(gateway): non-editable platforms deliver long replies once — interim finals join the delivery ledger (#117272, salvage #117286)

merged to main

files: gateway/run_turn_runner.py, tests/gateway/test_run_progress_topics.py

2 PRs closed without merging

From the close comments: merged via another change 2

#117278 fix(gateway): no interim lane without a stream consumer · merged via another change → 4774bb0, #117635
#117286 fix(gateway): stop non-editable platforms from sending replies twice · merged via another change → 4774bb0, #117635

Closed issues · 1

Closed#117272[Bug]: Weixin (non-editable platform) delivers every long reply twice — interim callback falls back to a plain send when no stream consumer exists

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.50: 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: #117635
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 21 Sep 2026

For your agent

The same facts, typed.

cluster/117272.json
cluster/117272.md