{"repo":"NousResearch/hermes-agent","public_id":"33389","display_label":"Honoring explicit Gemini provider for vision configuration","summary":"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.","subsystem":"agent","counts":{"members":3,"open_issues":0,"open_issues_distinct":0,"open_prs":0,"closed_issues":1,"merged_prs":0,"attempt_prs":2},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[],"members":[{"kind":"issue","number":33389,"title":"auxiliary.vision.provider: gemini explicit configuration is not honored — falls through to main provider or fails","url":null,"state":"closed"},{"kind":"pr","number":33427,"title":"fix(vision): honor explicit gemini provider in resolve_vision_provider_client","url":null,"state":"closed","close_reason":{"refs":[{"kind":"commit","value":"a8841e2a6877f7b5e7b4b6ab0122ef2fde229fe2","number":0},{"kind":"pr","value":"#33389","number":33389}],"category":"implemented_elsewhere","implication":"superseded"},"merged":false,"is_fix_pr":true,"fix_tier":"suggested","fix_detail_withheld":true},{"kind":"pr","number":41420,"title":"fix: route vision to Gemini OpenAI-compatible endpoint","url":null,"state":"closed","close_reason":{"refs":[{"kind":"commit","value":"a8841e2a6877f7b5e7b4b6ab0122ef2fde229fe2","number":0}],"category":"implemented_elsewhere","implication":"superseded"},"merged":false,"is_fix_pr":true,"fix_tier":"suggested","fix_detail_withheld":true}],"trust":{"default_tier":"verified","includes_suggested":false}}