Cairn

API error body extraction and classification fixes

NousResearch/hermes-agent · cluster 14195 · agent

Data as of

Nothing open on GitHub. Fix merged in #53582. Check it covers your case.

The short answer

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

Multiple fixes and a feature addressing how wrapped or nested API errors are inspected, with cause-chain walking to correctly extract error bodies and improve error classification for failover logic. One member about preserving tool-turn context appears adjacent but not fully aligned with the core theme.

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.

  • #53582 fix(agent): walk cause chain when extracting wrapped API error bodies (salvage of #14287 by @LeonSGP43)

    merged to main

    files: agent/error_classifier.py, tests/agent/test_error_classifier.py

5 PRs closed without merging

From the close comments: done elsewhere 1 · stale or abandoned 1 · superseded by another PR 1 · other 2

  • #14219 fix(agent): preserve nested error bodies during classification · stale or abandoned
  • #14287 fix(agent): preserve nested API error bodies · done elsewhere → e7c0134
  • #14349 fix(agent): inspect wrapped API error bodies · other → #53582, #14287, #14195
  • #14787 fix(agent): make _extract_error_body walk cause chain to match _extract_status_code · other → #53582, #14287, #14195
  • #16952 fix: preserve tool-turn context and harden issue follow-ups · superseded by another PR → #52618, #14185, #14785
Closed issues · 1
  • Closed#14195Wrapped API errors lose nested body details and misclassify transient 402s as billing failures
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.29: 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
Merged PRs
#53582
Closed issues
1
Attempts
5 PRs closed without merging
Fix link checked
27 Jun 2026

For your agent

The same facts, typed.

cluster/14195.json
cluster/14195.md