NousResearch/hermes-agent

Gateway retry noise and chat reply interference fixes

Cluster 101138 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These items address a filter that misses certain retry message formats and a code path where retry diagnostics can appear in place of or alongside actual chat responses. Related work also covers liveness probing on idle connections.

Open issues1

  • Issue#101138Telegram status-noise filter misses the current retry format, and the final-response path never consults it at all

Open PRs1

  • PR#101157fix(gateway): stop retry diagnostics from replacing chat replies

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #101158 fix(gateway): cover counter retry format and noise-filter the final response · superseded by another PR → #101157, #101138
  • #101258 fix(buzz): probe liveness on read idle before reconnecting; fix(gateway): stop empty-response retry noise on chats (#101160, #101138) · done elsewhere → #98097
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

Subsystem
gateway
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.