[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
agent-browser (source)	0.40.0 → 0.41.0

---

Release Notes

vercel-labs/agent-browser (agent-browser)

v0.41.0

Compare Source

Breaking Changes

• @agent-browser/eve tools now come from the MCP tool catalog. The extension exposes the CLI's MCP tools instead of 21 hand-written ones, so tool names and inputs change: navigate is open, evaluate is eval, press_key is press, select_option is select, set_checked is check and uncheck, get is get_text, get_url and the other get_* tools, tabs is the tab_* tools, and wait_for is the wait_* tools. The same names apply to @agent-browser/eve/tools overrides. The sandbox needs agent-browser 0.41, which the extension installs by default (#​2241)

New Features

• Added agent-browser mcp call <tool> '<json>' to run one MCP tool without a stdio session and print its result as JSON with the agent-browser version, for runtimes that cannot keep a process open between tool calls (#​2238)
• Added @agent-browser/sandbox/mcp-tools.json, every MCP tool with its title, description, input schema, annotations and profiles, generated from the CLI and checked by a test (#​2240)

Improvements

• @agent-browser/eve runs each tool as its own short-lived process, so no agent-browser process outlives a tool call. The 28 core tools are listed to the model and the other 14 are deferred, found with eve__search, which keeps the listed tool context at its previous size (#​2241)

Bug Fixes

• MCP tool arguments can no longer set global flags. The CLI reads global flags anywhere in its arguments, so a value such as a selector or extraArgs entry could carry its own --allowed-domains and override the server or caller allowlist. Tool calls that try are now rejected (#​2238)

Contributors

• @​Railly
• @​lahfir

---

Configuration

📅 Schedule: (in timezone Asia/Jerusalem)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

Summary by CodeRabbit

• Updates
  • The browser automation runtime is now version 0.41.0. Runtime version checks are aligned with the update, while the existing browser executable and communication setup remain unchanged.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: paseo-shared-browser/npm-shrinkwrap.json

npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code EUNSUPPORTEDPROTOCOL
npm error Unsupported URL Type "catalog:": catalog:
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-11-01T04_24_32_508Z-debug-0.log

[coderabbitai]

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 6aca7790-ca48-4021-a393-6f53aa650da2

Commits

Reviewing files that changed from the base of the PR and between 6fea779 and 3386a6e.

Files ignored due to path filters: 1

• bun.lock is excluded by !**/*.lock

Files selected for processing: 7

• paseo-shared-browser/README.md
• paseo-shared-browser/npm-shrinkwrap.json
• paseo-shared-browser/package.json
• paseo-shared-browser/scripts/prepare-runtime.mjs
• paseo-shared-browser/server/agent-browser-runtime.ts
• paseo-shared-browser/server/runtime-launch-environment.test.ts
• paseo-shared-browser/server/runtime-video-opt-in.test.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 8 remain after this review.

Walkthrough

The plugin updates its agent-browser dependency and runtime version checks from 0.40.0 to 0.41.0. The README and test fixtures use the new version. The shrinkwrap also updates hono from 4.13.14 to 4.13.16.

Changes: Runtime version update

Layer / File(s)	Summary
Synchronize agent-browser version paseo-shared-browser/package.json, paseo-shared-browser/npm-shrinkwrap.json, paseo-shared-browser/scripts/prepare-runtime.mjs, paseo-shared-browser/server/agent-browser-runtime.ts, paseo-shared-browser/server/runtime-launch-environment.test.ts, paseo-shared-browser/server/runtime-video-opt-in.test.ts, paseo-shared-browser/README.md	The dependency, runtime checks, test fixtures, and README now use agent-browser 0.41.0. The shrinkwrap also updates hono to 4.13.16.

Estimated code review effort: 1 (Trivial) | ~4 minutes

Change: Other

Possibly related issues

• Issue 1 tracks Renovate updates and lists the agent-browser update to 0.41.0 applied here.

Possibly related PRs

• omercnet/paseo-plugins#441: Updates the same dependency and runtime pins from 0.39.4 to 0.40.0.
• omercnet/paseo-plugins#428: Updates the same dependency, runtime pins, documentation, lockfile, and version tests.
• omercnet/paseo-plugins#404: Updates the same dependency and related runtime-version files.

Suggested reviewers: omercnet

Merge Risk: Minimal · up to 3386a

The update is mergeable: version checks and runtime lifecycle remain compatible, with no concrete regression identified.

Security architecture risk: Low · up to 3386a

The browser-control dependency changes, but the review found no new public entrypoint or demonstrated weakening of an existing control. The new executable’s behavior has not been fully verified, so some compatibility and cleanup uncertainty remains.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

• inferred — The changed executable receives the runtime’s browser-session authority, including its configured profile and IPC location. The observed repository change does not establish a new cross-workspace or remote entrypoint; the effective behavior of the new dependency remains the principal exposure uncertainty.

Security Findings and Attack Paths

• inferred — No PR-introduced attacker-to-executable command path was established: the compared production runtime changes only its version constant. Neither a foreign-session close outcome nor an introduced security regression is verified.

Trust Boundaries and Controls

• observed — The runtime checks the executable’s reported version and uses an owner nonce and process identity before direct termination. The session-scoped close command does not carry that ownership proof.

Resilience and Maintainability Implications

• observed — Shutdown waits for an in-progress open, checks for daemon exit, and escalates to verified-owned termination when necessary. The new package’s complete process-lifecycle behavior was not exercised here.

Hardening Proposals

• proposed — Before rollout, verify startup, session collision, close, and cleanup against the packaged 0.41.0 executable; consider requiring ownership proof before session-scoped close and metadata removal.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: updating the agent-browser dependency to version 0.41.0.
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 4 files. (3 skipped: 3 unsupported.)

Finishing Touches

Generate docstrings

• Commit to this branch
• Create a new PR

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

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

Warning

Some tools did not complete. Review the errors below.

Biome (2.5.15)

paseo-shared-browser/npm-shrinkwrap.json

Biome could not lint this file: nested root configuration. Check the repository's Biome configuration and plugins.

paseo-shared-browser/package.json

Biome could not lint this file: nested root configuration. Check the repository's Biome configuration and plugins.

paseo-shared-browser/scripts/prepare-runtime.mjs

Biome could not lint this file: nested root configuration. Check the repository's Biome configuration and plugins.

• 3 others