# NousResearch/hermes-agent · Cloud browser fallback to local Chromium on failure

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #10984. Verify it addresses your case.
- **Recommended:** read PR #10984 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-10984`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #10883: \[Bug\]: Cloud browser provider has no runtime fallback to local Chromium when API fails

## Prior & competing PRs

- **#10984: fix(browser): runtime fallback to local Chromium when cloud provider fails**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `tests/tools/test_browser_cloud_fallback.py`, `tools/browser_tool.py`
- **#10895: fix(browser): runtime fallback to local Chromium when cloud provider fails**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#10984`

## Fix status

- Merged to main in PR #10984 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-04-16`. This confirmation is old and may be out of date (a revert/reopen would not have invalidated it here); re-verify.