Cairn

Image routing, vision detection, and queue-blocking fixes

NousResearch/hermes-agent · cluster 638 · agent

Data as of

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

The short answer

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

These items address multimodal image routing based on model vision capability, fallback behavior when providers reject image input, and a message queue blockage caused by image-related errors. Specific providers mentioned include Nous API and OpenRouter.

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.

  • #53901 fix(image-routing): unblock message queue on OpenRouter 'no endpoints' image 404 (#21160)

    merged to main

    files: agent/conversation_loop.py, tests/run_agent/test_image_rejection_fallback.py

2 PRs closed without merging

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

  • #670 fix: vision support detection + image error recovery (#638) · other
  • #21198 fix(image-routing): strip images and retry as text when provider rejects image input · superseded by another PR → #53901, #21160
Closed issues · 2
  • Closed#638[Bug]: Image messages break Nous API models — no vision support detection or error recovery
  • Closed#21160Image routing failure locks entire message queue — subsequent text messages blocked
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.34: 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
#53901
Closed issues
2
Attempts
2 PRs closed without merging
Fix link checked
28 Jun 2026

For your agent

The same facts, typed.

cluster/638.json
cluster/638.md