Cairn
NousResearch/hermes-agent

Agent failure state not surfaced in responses API

Cluster 102921 · gateway. 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.

A bug where the /v1/responses endpoint returns provider or agent failures as successful completed messages rather than exposing the failure state. Fixes cover both response status and HTTP error codes for non-streaming responses.

Open issues1

  • Issue#102921[Bug]: /v1/responses returns provider failures as successful assistant messages (status hardcoded to "completed") — #22496 fixed only chat/completions

Open PRs1

  • PR#102939fix(api_server): surface /v1/responses agent failures as 502, not completed

1 PR closed without merging

From the close comments: duplicate 1

  • #103676 fix(api): surface agent failure state on non-streaming responses (fixes #102921) · duplicate → #102939
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
gateway
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/102921.json
cluster/102921.md