Cairn
NousResearch/hermes-agent

Honoring explicit Gemini provider for vision configuration

Cluster 33389 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items all concern the auxiliary vision provider setting when it is explicitly set to Gemini. One issue reports the setting not being honored, and two pull requests propose changes to route vision requests to Gemini or respect that provider in resolve_vision_provider_client.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 2

  • #33427 fix(vision): honor explicit gemini provider in resolve_vision_provider_client · done elsewhere → a8841e2, #33389
  • #41420 fix: route vision to Gemini OpenAI-compatible endpoint · done elsewhere → a8841e2
Closed issues · 1
  • Closed#33389auxiliary.vision.provider: gemini explicit configuration is not honored — falls through to main provider or fails
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
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/33389.json
cluster/33389.md