NousResearch/hermes-agent
Cloud browser fallback to local Chromium on failure
Cluster 10883. Data as of
Nothing open on GitHub. Fix merged in #10984 on 16 Apr 2026. Check it covers your case.
The short answer
0open issues
0open PRs
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #10984. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #10984. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug was reported and addressed regarding the absence of a runtime fallback to local Chromium when a cloud browser provider's API fails. The members all concern this same specific gap in fallback behavior.
Open issues0
Open PRs0
Fixes on record
-
#10984 fix(browser): runtime fallback to local Chromium when cloud provider fails
files:
tests/tools/test_browser_cloud_fallback.py,tools/browser_tool.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#10895 fix(browser): runtime fallback to local Chromium when cloud provider fails · merged via another change →
#10984
Closed issues · 1
- Closed#10883[Bug]: Cloud browser provider has no runtime fallback to local Chromium when API 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.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 LabAt a glance
- Merged PRs
- #10984
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 16 Apr 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.