Cairn
NousResearch/hermes-agent

browser_vision tool visibility and routing fixes

Cluster 47149 · agent. Data as of

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

The short answer

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

These items address bugs in how browser_vision is advertised or hidden from the model depending on provider vision capabilities and native fast-path status. Related changes also fix routing of auxiliary vision providers.

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.

  • #110208 Vision tools stay visible for native-vision mains and main-alias aux pins (#47149, #97310, salvage #97763)

    merged to main

    files: apps/desktop/src/app/settings/model-settings.test.tsx, apps/desktop/src/app/settings/model-settings.tsx, contributors/emails/[redacted:email], hermes_cli/web_server_config.py, tests/agent/test_vision_routing.py, tests/hermes_cli/test_stale_aux_local_endpoint.py, tools/vision_tools.py

3 PRs closed without merging

From the close comments: done elsewhere 2 · other 1

  • #47151 fix(browser): unhide browser_vision when native fast path is active · done elsewhere
  • #47227 fix(browser): advertise browser_vision when main model supports vision natively (#47149) · other
  • #65390 fix(vision): split per-tool vision/video gates so native fast path only advertises image · done elsewhere → 53183d5, #110208
Closed issues · 1
  • Closed#47149browser_vision hidden from the model when main model is vision-capable on a non-allowlisted provider
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.40: 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
#110208
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
13 Sep 2026

For your agent

The same facts, typed.

cluster/47149.json
cluster/47149.md