NousResearch/hermes-agent

Image 400 error recovery to prevent session bricking

Cluster 69078 · agent. Data as of 2026-10-28 11:56 UTC

Nothing open on GitHub. Fix merged in #97059 on 28 Aug 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 #97059. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #97059. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #97059 Pick up a Lab task

These issues and fixes address cases where invalid or corrupt image errors (400 responses) from AI providers permanently break agent sessions. The work involves detecting such errors and retrying with stripped images instead of halting the session.

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.

#97059 fix(agent): corrupt-image 400s recover via strip-and-retry instead of bricking the session (#69078, salvage #69104)

merged to main

files: agent/conversation_loop.py, agent/error_classifier.py, contributors/emails/[redacted:email], contributors/emails/[email protected], tests/agent/test_error_classifier.py, tests/run_agent/test_69078_image_corrupt_recovery.py, tests/run_agent/test_image_rejection_fallback.py

1 PR closed without merging

From the close comments: merged via another change 1

#69104 fix(agent): recover from xAI Invalid PNG image 400 that permanently bricks sessions · merged via another change → #97059, #81326, #29864, #69078

Closed issues · 1

Closed#69078[Bug]: xAI grok-4.5 'Invalid PNG image' 400 permanently bricks session — evades all image-recovery matchers; source image verified valid (xAI variant of #25837)

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
Merged PRs: #97059
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 28 Aug 2026

For your agent

The same facts, typed.

cluster/69078.json
cluster/69078.md