Cairn
NousResearch/hermes-agent

Expose tool call success/failure signals in responses

Cluster 73389 · 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.

These members all concern the lack of visibility into whether tool calls within a completion or agent run actually succeeded, and request that success/failure counts or signals be surfaced in API responses and agent outputs.

Open issues1

  • Issue#73389[Feature/Bug]: No signal exposed to indicate whether a completed run's tool calls actually succeeded - a session with zero working tools can still return a confident, well-formed disposition

Open PRs1

  • PR#73585feat(agent): expose signal for whether completion carries tool calls

1 PR closed without merging

From the close comments: partial fix 1

  • #73805 feat(api): expose tool call success/failure counts in chat/completions response · partial fix → 8aa229a, #73389, #73585, #73805, #1, #15803, #14532, #6, #9, #374151, #4338
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

Subsystem
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/73389.json
cluster/73389.md