NousResearch/hermes-agent
Empty-response calls on internal-notification turns after final delivery
Cluster 135816 · agent. Data as of
2 open items. Fix attempted, not merged.
The short answer
1open issue
1open PR
3items grouped
- Known?
- Yes. 3 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR 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.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskA field report describes late internal completions leading to 12 empty-response calls with an estimated cost of about $8.95 after final delivery. Two pull requests propose changes to how empty replies on runtime/internal-notification turns are handled, one by exiting quietly and one by collapsing the paid empty-retry step.
Open issues1
- Issue#135816[Bug][Field report]: late internal completions cause 12 empty-response calls (~$8.95 estimated) after final delivery
Open PRs1
- PR#139767fix(turn): quiet exit on empty reply to machinery turns
1 PR closed without merging
From the close comments: done elsewhere 1
-
#135914 fix(agent): collapse the paid empty-retry rung on machinery (internal-notification) turns · done elsewhere →
f74fbb0,#139767
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.00means 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 LabAt a glance
- Subsystem
- agent
- Closed issues
- 0
- Attempts
- 1 PR closed without merging