Skip to content

Update agent-browser to 0.41.1 - #1269

Merged
bryan-minimal merged 8 commits into
mainfrom
update-agent-browser-0.41.1
Nov 3, 2026
Merged

bryan-minimal merged 8 commits into
mainfrom
update-agent-browser-0.41.1

Conversation

@gominimal-pkgmgr-mgr

Copy link
Copy Markdown
Contributor

Update agent-browser 0.15.1 → 0.41.1

Source: github:vercel-labs/agent-browser
Release: 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)

Pkgscan: clean — diff against the prior version surfaced no newly-introduced suspicious patterns.

Components changed

CycloneDX component delta (declared materials — the package's own version, not a dependency-tree diff)
Component Old New
~ agent-browser 0.15.1 0.41.1
~ agent-browser-upstream 0.15.1 0.41.1

Changes

Old New
Version 0.15.1 0.41.1
SHA256 c30724a5fba1beb2... b3d9d60b8a38f05e...
Size 515 KB 2.6 MB
Source gs://minimal-staging-archives/vercel-labs/agent-browser/v0.15.1.tar.gz gs://minimal-staging-archives/vercel-labs/agent-browser/v0.41.1.tar.gz
  • License: Apache-2.0 (source: GitHub + tarball)

🔒 TLS: github.com — Sectigo Public Server Authentication CA DV E36 → Sectigo Public Server Authentication Root E46 (root c90f26f0fb1b4018…) · TLSv1_3 · TLS13_AES_128_GCM_SHA256 · X25519 ⇒ codeload.github.com — Sectigo Public Server Authentication CA DV E36 → Sectigo Public Server Authentication Root E46 (root c90f26f0fb1b4018…) · TLSv1_3 · TLS13_AES_128_GCM_SHA256 · X25519


Created by pkgmgr

@gominimal-pkgmgr-mgr
gominimal-pkgmgr-mgr Bot requested a review from a team as a code owner November 2, 2026 20:11
@coderabbitai

coderabbitai Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

bryan-minimal and others added 6 commits November 2, 2026 12:22
…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>
@bryan-minimal

Copy link
Copy Markdown
Member

Recipe ported to 0.41.1 (head 0084f27a)

The bot's sha bump alone would not build. Upstream 0.20.0 removed the Node.js daemon (vercel-labs/agent-browser#754). 0.41.1 is a native Rust CLI, and the npm package's bin/agent-browser.js is only a launcher that picks a per-platform binary. The old recipe ran pnpm build and shipped dist/ + node_modules; neither exists any more.

What ships now

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

  1. Dashboard first, as upstream's build:source does. cli/src/native/stream/http.rs embeds packages/dashboard/out with rust-embed. Without it, cli/build.rs writes a "Dashboard not built" placeholder and agent-browser dashboard serves that.
    • Install: pnpm install --frozen-lockfile --ignore-scripts --filter dashboard.
    • Next.js's random buildId is pinned with generateBuildId, the same fix as packages/next.
    • NEXT_TELEMETRY_DISABLED=1.
    • pnpm is told not to fetch the packageManager: pnpm@11.1.3 pin; the log shows pnpm v12.17.0.
    • next/font/google downloads Geist at build time. The build already has network through rust's needs.
  2. cargo build --release --locked. The old recipe had no --locked. RUSTFLAGS remap and CONST_RANDOM_SEED are 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-path still exists, but the daemon's own auto-launch (native/actions.rs), mcp mode and doctor read 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, and doctor, install, upgrade, chat and 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/certs instead. Our ca-certificates drops 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-certificates is 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: record
  • certutil: --ca-cert into Chromium's NSS db
  • npx appium: iOS
  • lightpanda / obscura: --engine
  • Xvfb: 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! of axe.min.js), and its bundled third-party code is MIT/ISC.
  • React DevTools installHook.js is 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.lock against 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: exact agent-browser 0.41.1
  • skills: list + get core
  • layout: no node/node_modules, licence texts present
  • dashboard_embedded: the binary contains the real export's metadata and not the placeholder string
  • open_check: open a data: URL through chromium; a follow-up get title in the same shell reaches the same daemon
  • distrust_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 compiled agent-browser v0.41.1 with no placeholder warning.
  • min check --packages agent-browser: every check passes, including standalone tests, enumerate bins and missing runtime_deps.
  • Negative control: version_check changed to expect 9.9.9 failed 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/node and node_modules are 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.lock with 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 by agent-browser install, which downloads Chrome for Testing. The 0.15.1 recipe had no lock patch either. This wants pkgmgr lock-patch agent-browser run where PKGMGR_CARGO exists (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 build check 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>
@bryan-minimal
bryan-minimal added this pull request to the merge queue Nov 3, 2026
Merged via the queue into main with commit eb03cf0 Nov 3, 2026
13 checks passed
@bryan-minimal
bryan-minimal deleted the update-agent-browser-0.41.1 branch November 3, 2026 04:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant