NousResearch/hermes-agent
Chromium install behavior for cloud vs local setups
Cluster 51237 · agent. Data as of
Nothing open on GitHub. Fix merged in #86240 on 14 Aug 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 #86240. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address how the browser setup handles Chromium installation, specifically detecting missing Chromium, providing clearer errors, and skipping unnecessary local installs when using cloud providers or constrained environments like Termux/Android.
Open issues0
Open PRs0
Fixes on record
-
#86240 fix: install Browser Use CLI for every browser backend except Camofox
files:
hermes_cli/tools_config.py,tests/hermes_cli/test_tools_config.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#51293 fix(browser): skip Chromium install for cloud setup · done elsewhere →
#86240
Closed issues · 1
- Closed#51237[Bug]: Browser setup unnecessarily installs local Chromium for cloud providers — fails on Termux/Android
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
- Subsystem
- agent
- Merged PRs
- #86240
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 14 Aug 2026