Cairn
NousResearch/hermes-agent

Tool boundary preamble fragmentation fixes in gateway

Cluster 99026. Data as of

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

The short answer

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

These issues and fixes relate to a gateway bug where accumulated tool progress is incorrectly split or fragmented at tool boundaries, including during hot-reloaded adapters and transient previews. The work focuses on preserving progress continuity across these boundaries.

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.

  • #121694 fix(gateway): survive hot-reloaded adapters and stop tool-boundary preambles fragmenting progress (#72628, #99026)

    merged to main

    files: gateway/stream_consumer.py, gateway/stream_consumer_transport.py, tests/gateway/test_stream_consumer.py, tests/gateway/test_stream_consumer_draft.py, tests/gateway/test_stream_consumer_hot_reload.py

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

  • #99046 fix(gateway): gate sub-floor preamble finalizes on tool boundaries · merged via another change → a7c44e9, #121694, #99026
  • #99073 fix(gateway): preserve progress across transient previews · superseded by another PR → a7c44e9, #121694, #99026
Closed issues · 1
  • Closed#99026[Bug]: Telegram draft boundaries split accumulated tool progress into one message per tool
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
#121694
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
24 Sep 2026

For your agent

The same facts, typed.

cluster/99026.json
cluster/99026.md