Repository navigation
Update agent-browser to 0.41.1 - #1269
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
…e dashboard 0.20.0 removed the Node.js daemon (upstream #754). The npm package's bin/agent-browser.js only picks a per-platform binary, so the recipe no longer runs `pnpm build` or ships dist/, node_modules or a node runtime. - Build the dashboard (Next.js static export) first, as upstream's `build:source` does: cli/src/native/stream/http.rs embeds packages/dashboard/out with rust-embed, and cli/build.rs otherwise embeds a "Dashboard not built" placeholder. Pin Next's buildId, disable Next telemetry, keep pnpm from fetching the pinned pnpm 11.1.3. - `cargo build --locked`. - Install the binary under usr/libexec/agent-browser/bin with skills/ and skill-data/ beside it (skills.rs / chat.rs look them up relative to the binary's canonical path). Ship the axe-core licence files. - Wrapper: AGENT_BROWSER_EXECUTABLE_PATH defaults to chromium-bin's /usr/bin/chromium (CVE-2026-111943; the env var also reaches the daemon auto-launch, mcp and doctor paths), and AGENT_BROWSER_USE_SYSTEM_CA=1 so the CLI's own HTTPS (`read` etc.) verifies against ca-certificates rather than its compiled-in webpki-roots 1.0.5. ca-certificates becomes a runtime dep. - runtime_deps: drop node-lts; add ca-certificates. - license_spdx lists what the binary compiles in (axe-core MPL-2.0, CDP protocol BSD-3-Clause, Geist OFL-1.1, MIT/ISC JS). - Tests: version, skills, dashboard embedded, open + get title, and the distrust/system-CA wiring. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Inside the recursive tests record, a field named `version` made
%{version} refer to the test record itself.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Checked every registry crate in cli/Cargo.lock against crates.io: beyond MIT OR Apache-2.0 the binary links ISC (ring, rustls-webpki, untrusted), Unicode-3.0 (icu_*), BSD-2-Clause (rav1e), BSD-3-Clause (subtle, exr), Zlib (zlib-rs, foldhash), CDLA-Permissive-2.0 (webpki-roots) and MPL-2.0 (option-ext). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The daemon does not outlive a test command, so `get title` as its own command met a fresh daemon on about:blank. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Recipe ported to 0.41.1 (head
|
| path | what |
|---|---|
usr/bin/agent-browser |
4-line bash wrapper (below) |
usr/libexec/agent-browser/bin/agent-browser |
the Rust binary, about 16 MB stripped. It compiles in the dashboard, axe-core and the CDP protocol types |
usr/libexec/agent-browser/{skills,skill-data} |
served by agent-browser skills / the MCP skills_* tools. skills.rs finds them at <canonical exe dir>/../skill-data/core/SKILL.md, so they must sit beside bin/ |
usr/share/licenses/agent-browser/ |
LICENSE, LICENSE-axe-core.txt, LICENSE-axe-core-THIRD-PARTY.txt (upstream's package.json ships the latter two) |
There is no node at runtime and no node_modules. node-lts + pnpm remain build deps, but only to build the dashboard.
Build
- Dashboard first, as upstream's
build:sourcedoes.cli/src/native/stream/http.rsembedspackages/dashboard/outwith rust-embed. Without it,cli/build.rswrites a "Dashboard not built" placeholder andagent-browser dashboardserves that.- Install:
pnpm install --frozen-lockfile --ignore-scripts --filter dashboard. - Next.js's random buildId is pinned with
generateBuildId, the same fix aspackages/next. NEXT_TELEMETRY_DISABLED=1.- pnpm is told not to fetch the
packageManager: pnpm@11.1.3pin; the log showspnpm v12.17.0. next/font/googledownloads Geist at build time. The build already has network through rust'sneeds.
- Install:
cargo build --release --locked. The old recipe had no--locked. RUSTFLAGS remap andCONST_RANDOM_SEEDare kept.
Wrapper defaults (a caller's env var or flag still wins)
AGENT_BROWSER_EXECUTABLE_PATH=/usr/bin/chromium: chromium-bin's full browser, for the CVE-2026-111943 distrust policy.--executable-pathstill exists, but the daemon's own auto-launch (native/actions.rs),mcpmode anddoctorread the env var, so the env var covers more paths than the old prepended flag did.AGENT_BROWSER_USE_SYSTEM_CA=1: new in this range, the CLI makes its own HTTPS requests.read <url>fetches arbitrary pages without a browser, anddoctor,install,upgrade,chatand plugins do the same. By default these verify against the compiled-in webpki-roots 1.0.5, which predates the emSign distrust (RUSTSEC-2026-0381). With this variable set they use/etc/ssl/certsinstead. Ourca-certificatesdrops both anchors (emSign ECC Root CA - G3 and AAA Certificate Services), so the older rustls-webpki doesn't matter for this CVE. This follows AGENTS.md "Do not embed a trust store".ca-certificatesis now a runtime dep.
runtime_deps
bash, glibc, chromium-bin, ca-certificates. node-lts is dropped.
I left out some optional tools the binary shells out to:
ffmpeg:recordcertutil:--ca-certinto Chromium's NSS dbnpx appium: iOSlightpanda/obscura:--engineXvfb: headed mode without a display
license_spdx
The old value was Apache-2.0. The new one is Apache-2.0 AND MPL-2.0 AND MIT AND ISC AND BSD-2-Clause AND BSD-3-Clause AND Unicode-3.0 AND Zlib AND CDLA-Permissive-2.0 AND OFL-1.1.
- axe-core 4.12.1 is MPL-2.0 (
include_str!ofaxe.min.js), and its bundled third-party code is MIT/ISC. - React DevTools
installHook.jsis MIT. - The CDP protocol JSON is BSD-3-Clause.
- Geist, self-hosted into the dashboard, is OFL-1.1.
- I checked all 343 registry crates in
cli/Cargo.lockagainst crates.io:- ISC: ring, rustls-webpki, untrusted
- Unicode-3.0: icu_*
- BSD-2-Clause: rav1e
- BSD-3-Clause: subtle, exr, ravif
- Zlib: zlib-rs, foldhash
- CDLA-Permissive-2.0: webpki-roots
- MPL-2.0: option-ext
- I read the dashboard's production dependency closure from pnpm-lock (723 packages, only part of it bundled into the export). It is mostly MIT, plus ISC, Apache-2.0 and BSD-3-Clause (d3 / mermaid via streamdown). Smaller pieces: dompurify
MPL-2.0 OR Apache-2.0, tslib 0BSD, robust-predicates Unlicense. I did not inspect the built bundle, so those few aren't in the expression.
Tests
version_check: exactagent-browser 0.41.1skills: list +get corelayout: no node/node_modules, licence texts presentdashboard_embedded: the binary contains the real export's metadata and not the placeholder stringopen_check:opena data: URL through chromium; a follow-upget titlein the same shell reaches the same daemondistrust_policy_wired: both wrapper defaults, the chromium policy,/etc/ssl/certs/ca-certificates.crt
Verified (min session box, arm64, builds on res-server)
min package build --rebuild --verbose agent-browser:build finished. Next 16.1.1 (Turbopack) exported/, then cargo compiledagent-browser v0.41.1with no placeholder warning.min check --packages agent-browser: every check passes, including standalone tests, enumerate bins and missing runtime_deps.- Negative control:
version_checkchanged to expect9.9.9failed as it should. - Tree, read from inside the test sandbox:
usr/libexec/agent-browser/{bin/agent-browser (16,455,048 B), skills/agent-browser, skill-data/{agentcore,core,derive-client,dogfood,electron,protected-vercel-deployments,slack,vercel-sandbox,webmcp-gen}}usr/share/licenses/agent-browser/(3 files)- 17 MB in total.
/usr/bin/nodeandnode_modulesare absent.
- Reproducibility: two
--rebuilds gave an identical tree hash (409497ba…) and binary hash (3c5e3f11…). That covers arm64 only.
Not done here, needs a call
-
Rust lock floors. OSV lists advisories against
cli/Cargo.lockwith fixed releases:- rustls 0.23.37 → 0.23.46 (RUSTSEC-2026-0285/0346/0348/0349)
- rustls-webpki 0.103.13 → 0.103.16 (-0382)
- webpki-roots 1.0.5 → 1.0.10 (-0381)
- tokio 1.49.0 → 1.51.6 (-0386)
- quinn-proto 0.11.17 → 0.11.18
- anyhow → 1.0.103, crossbeam-epoch → 0.9.20, rand → 0.8.6 / 0.9.3
zip 8.2.0 also has advisories, but its fixes need 9.x, which Cargo.toml's
zip = "8.2.0"excludes. zip is used only byagent-browser install, which downloads Chrome for Testing. The 0.15.1 recipe had no lock patch either. This wantspkgmgr lock-patch agent-browserrun wherePKGMGR_CARGOexists (Cloud Build), not a hand patch. -
MPL-2.0 corresponding source: the mirrored tarball carries axe-core only as
axe.min.js. If we want the preferred form available, mirror dequelabs/axe-core v4.12.1. -
amd64 was not built locally; the build-bot's
minimal buildcheck covers it.
The build-bot's test sandbox has no unprivileged user namespaces, so Chromium aborted with "No usable sandbox!" on both arches (pkgs#1269 run f870d701). chromium-bin's own launch test passes --no-sandbox for the same reason. Set via AGENT_BROWSER_ARGS inside the two test shells only; the shipped wrapper keeps Chromium's sandbox. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Update agent-browser
0.15.1→0.41.1Source:
github:vercel-labs/agent-browserRelease: https://github.com/vercel-labs/agent-browser/releases/tag/v0.41.1
Changelog: vercel-labs/agent-browser@v0.15.1...v0.41.1
Released: 1 days ago (2026-11-01)
Components changed
CycloneDX component delta (declared materials — the package's own version, not a dependency-tree diff)
agent-browser0.15.10.41.1agent-browser-upstream0.15.10.41.1Changes
0.15.10.41.1c30724a5fba1beb2...b3d9d60b8a38f05e...gs://minimal-staging-archives/vercel-labs/agent-browser/v0.15.1.tar.gzgs://minimal-staging-archives/vercel-labs/agent-browser/v0.41.1.tar.gzApache-2.0(source: GitHub + tarball)🔒 TLS:
github.com— Sectigo Public Server Authentication CA DV E36 → Sectigo Public Server Authentication Root E46 (rootc90f26f0fb1b4018…) · TLSv1_3 · TLS13_AES_128_GCM_SHA256 · X25519 ⇒codeload.github.com— Sectigo Public Server Authentication CA DV E36 → Sectigo Public Server Authentication Root E46 (rootc90f26f0fb1b4018…) · TLSv1_3 · TLS13_AES_128_GCM_SHA256 · X25519Created by pkgmgr