Repository navigation
agent-browser: run against chromium-headless-shell-bin, not chromium-bin - #735
Merged
Merged
Conversation
chromium-bin has no future on arm64, and that is a sourcing dead end rather
than a stale pin:
* its arm64 leg came from Playwright's CDN, and Playwright STOPPED building
linux-arm64. r1243 was the last one ever (re-verified 2026-09-18 following
redirects: r1243 -> 200, r1245/1250/1260/1270 -> 400).
* Google publishes NO open-source Chromium binary for linux-arm64 at all.
The chromium-browser-snapshots bucket that chromium-bin's amd64 leg uses
is x64 ONLY (Linux_ARM64 -> 404), which is why an arm64 build had to come
from a third party in the first place.
* Chrome for Testing does build arm64, but the `chrome` bundle is branded
Google Chrome and ships libwidevinecdm.so. inbox#284 ruled that
non-redistributable and our cache redistributes.
chrome-headless-shell is the one artifact that clears all three: CfT builds
it for arm64, and pkgs#718 PROVED it redistributable — zero WidevineCdm
entries on either arch, and a LICENSE.headless_shell carrying the Chromium
BSD-3-Clause grant with none of the proprietary language.
WHAT THIS GIVES UP, stated plainly because it is a real reduction.
chrome-headless-shell is the separate, reduced headless binary — NOT the full
browser running headless — so these agent-browser features stop working:
--extensions no extension support in headless-shell
--headed this binary has no headed mode
WebGPU screenshots upstream documents these as requiring headed
agent-browser already defaults to headless (`--headed` is opt-in), and it is
driven by agents rather than humans: nothing runs it expecting a visible UI,
and no consumer uses extensions. That is the call being made here, not an
assumption that the binaries are equivalent.
Also worth recording: upstream's own default is to fetch CfT's `chrome`
bundle via `agent-browser install` — precisely the artifact we may not
redistribute. The explicit --executable-path is what keeps it from ever
reaching for that, so the flag is load-bearing for licensing, not just
convenience.
The way back, if extensions or WebGPU are ever needed: Debian ships chromium
for BOTH arches at 153.0.8010.52-1, Widevine-free and DFSG-free (verified:
0 WidevineCdm entries, `Files-Excluded: *.dll *.exe *.apk *.class`, licences
all BSD/Apache/MIT/MPL/LGPL with zero non-free entries). The cost is its
47-library runtime closure — libpulse, libopenh264, libdav1d, libFLAC,
libopus, libminizip, libXNVCtrl and friends, which Debian links dynamically
where Google's build bundles them.
Built and checked in the Linux sandbox: build finished, all 15 checkers pass
including missing-runtime_deps — which matters here, because swapping the
browser replaces the entire transitive system-lib closure.
chromium-bin now has no consumers in the tree. Left in place deliberately:
retiring it is a separate decision, and its amd64 leg is still a healthy
open-source source.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
Warning Review limit reached
This review includes 2 billable files and costs up to $0.50.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Or wait 23 minutes for your next included review. View limit detailsLimit details: You’ve used the included review currently available. Your 65 included PR review attempts over the past 7 days set your current allowance at 1 review per hour. Review configuration: ⚙️ Run configurationConfiguration used: Repository: gominimal/pkgs/.coderabbit.yaml Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (2)
Comment |
mitodrummer
approved these changes
Sep 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
chromium-binhas no future on arm64, and it's a sourcing dead end rather than a stale pin:chromium-browser-snapshotsbucket that chromium-bin's amd64 leg uses is x64 only (Linux_ARM64→ 404), which is why arm64 needed a third-party build in the first placechromebundle is branded Google Chrome and shipslibwidevinecdm.so— inbox#284 ruled that non-redistributable, and our cache redistributeschrome-headless-shellis the one artifact clearing all three: CfT builds it for arm64, and pkgs#718 proved it redistributable — zeroWidevineCdmentries on either arch, plus aLICENSE.headless_shellcarrying the Chromium BSD-3-Clause grant.What this gives up — stated plainly
chrome-headless-shellis the separate, reduced headless binary, not the full browser running headless. These agent-browser features stop working:--extensions--headedagent-browser already defaults to headless (
--headedis opt-in), and it's driven by agents rather than humans — nothing runs it expecting a visible UI, and no consumer uses extensions. That's the call being made here, not an assumption that the two binaries are equivalent.A licensing detail worth knowing
Upstream's own default is to fetch CfT's
chromebundle viaagent-browser install— precisely the artifact we may not redistribute. The explicit--executable-pathis what stops it ever reaching for that, so that flag is load-bearing for licensing, not just convenience.The way back
If extensions or WebGPU are ever needed: Debian ships chromium for both arches at 153.0.8010.52-1, Widevine-free and DFSG-free — verified 0
WidevineCdmentries,Files-Excluded: *.dll *.exe *.apk *.class, and licences all BSD/Apache/MIT/MPL/LGPL with zero non-free entries. The cost is its 47-library runtime closure (libpulse,libopenh264,libdav1d,libFLAC,libopus,libminizip,libXNVCtrl…), which Debian links dynamically where Google's build bundles them.Verification
Built and checked in the Linux sandbox:
build finished, all 15 checkers pass includingmissing runtime_deps— which matters here, because swapping the browser replaces the entire transitive system-lib closure.chromium-binnow has no consumers in the tree. Left in place deliberately — retiring it is a separate decision, and its amd64 leg is still a healthy open-source source.🤖 Generated with Claude Code