Cairn
NousResearch/hermes-agent

Classifying status-less streaming provider errors for failover

Cluster 62662 · agent. Data as of

Nothing open on GitHub. Fix merged in #121547 on 24 Sep 2026. Check it covers your case.

The short answer

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

The members concern streaming provider errors that arrive without a status_code (for example LM Studio Jinja render errors) and so bypass the 400 classifier, with one issue describing the turn ending silently without failover. The PRs propose classifying these errors as format_error so failover can apply; one also mentions body status codes and auxiliary fallback, and one is noted as superseding an earlier PR.

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.

  • #121547 fix(agent): classify status-less in-stream provider errors (body status code, render errors, aux fallback)

    merged to main

    files: agent/auxiliary_client.py, agent/error_classifier.py, tests/agent/test_auxiliary_client.py, tests/agent/test_error_classifier.py, tests/e2e/core/providers/test_chat_errors.py

2 PRs closed without merging

From the close comments: superseded by another PR 1 · other 1

  • #62673 fix: classify streaming render errors (no status_code) as format_error for failover · superseded by another PR → #64834
  • #64834 fix: classify streaming render errors as format_error + tests (supersedes #62673) · other → c342e78, #121547, #62662
Closed issues · 1
  • Closed#62662Streaming provider errors with no `status_code` (e.g. LM Studio Jinja render errors) bypass the 400 classifier and never fail over — turn dies silently
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
agent
Merged PRs
#121547
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
24 Sep 2026

For your agent

The same facts, typed.

cluster/62662.json
cluster/62662.md