NousResearch/hermes-agent

HTTP 400 oversize rejections bypass image-shrink recovery

Cluster 112473. Data as of 2026-10-26 12:29 UTC

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

open issues

open PRs

items grouped

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

Next step: read #113145, then check it covers your case.

Read #113145 Pick up a Lab task

A bug was identified where oversize request rejections returned as HTTP 400 (from providers like NVIDIA NIM, Alibaba DashScope, and Nebius) were not being routed to the image-shrink recovery path. The accompanying fixes address this routing gap so those responses correctly trigger the recovery mechanism.

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.

#113145 fix(agent): oversize image requests rejected as HTTP 400 now trigger the image-shrink recovery (#112473, salvage #111975)

merged to main

files: agent/error_classifier.py, agent/turn_api_error.py, agent/turn_recovery.py, tests/agent/test_image_shrink_recovery.py

1 PR closed without merging

From the close comments: merged via another change 1

#111975 fix(agent): route oversize rejections that arrive as HTTP 400 to the image-shrink recovery · merged via another change → 270fe15, 4655263, c159751, #112473

Closed issues · 1

Closed#112473[Bug]: Oversize request rejections reported as HTTP 400 bypass the image-shrink recovery (NVIDIA NIM, Alibaba DashScope, Nebius Token Factory)

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

Merged PRs: #113145
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 17 Sep 2026

For your agent

The same facts, typed.

cluster/112473.json
cluster/112473.md