Named custom provider vision override routing correction
Cluster 69709. Data as of
Nothing open on GitHub. Fix merged in #70118 on 23 Jul 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #70118. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #70071. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members address a bug where the supports_vision override was not being preserved or correctly applied when using named custom providers via the CLI --provider flag. The correction ensures named custom provider identity is retained during vision routing logic.
Open issues0
Open PRs0
Fixes on record
-
#70071 fix(vision): preserve named custom provider identity for vision routing
files:
agent/agent_init.py,agent/agent_runtime_helpers.py,agent/auxiliary_client.py,agent/chat_completion_helpers.py,agent/image_routing.py,agent/turn_context.py,cli.py,cron/scheduler.py,gateway/run.py,hermes_cli/cli_agent_setup_mixin.py,hermes_cli/oneshot.py,run_agent.py,tests/agent/test_credential_pool_routing.py,tests/agent/test_custom_providers_vision.py,tests/agent/test_turn_context.py,tests/gateway/test_agent_cache.py,tests/gateway/test_image_input_routing_runtime.py,tests/hermes_cli/test_cli_custom_provider_vision.py,tests/hermes_cli/test_runtime_provider_resolution.py,tui_gateway/server.py -
#70118 feat(image_routing): accept vision alias for custom provider models
files:
agent/image_routing.py,tests/agent/test_image_routing.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#69751 fix: preserve named custom provider vision overrides · merged via another change →
91546b8,#70071,#69896,#70118
Closed issues · 1
- Closed#69709supports_vision override not resolved for CLI --provider with named custom_providers
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.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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