Skip to content

v2.0.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 08 Nov 19:48
· 13 commits to main since this release
v2.0.0
3bdd4a6

Browser Bridge 2.0.0

Browser Bridge now runs on a standalone Go executable instead of Node.js. You can install and use the CLI, daemon, native host, and MCP server without a JavaScript runtime.

This release also adds per-tab action scheduling, outcome checks, visual comparisons, broader agent support, and more compact responses.

What changed since v1.15.0

Standalone installation

  • Native executables for macOS arm64/x64, Linux arm64/x64, and Windows x64.
  • Installers download the executable, verify its SHA-256 checksum, register the browser, and restart the daemon.
  • The extension setup panel provides installation commands matching its release line.
  • npm remains supported, but is now a bootstrap and launcher with zero runtime npm dependencies. It downloads the native runtime rather than shipping the old JavaScript implementation.
  • Native release selection is independent of the npm package version. BBX_VERSION supports an exact version or a release line such as 2.0.

Safer concurrent browser work

Page-changing operations now run through a per-tab queue. Actions targeting the same tab cannot overlap, while reads and operations on unrelated tabs remain concurrent.

Queued actions revalidate the document and access grant before execution. Cancellation and timeout handling keep a running action's slot occupied until browser execution settles.

input.perform also supports expected DOM, URL, and fetch/XHR response conditions. It returns OUTCOME_NOT_MET when those conditions are not observed. Dispatching a click or keystroke alone no longer needs to be treated as proof that a workflow succeeded.

Visual regression checks

New screenshot.baseline.create, compare, and release methods support scoped, exact pixel comparisons.

Results include changed-pixel counts and bounded before/after crops when useful. Baselines stay in memory, expire after five minutes, and are invalidated by navigation or access teardown. Visual comparisons supplement structured DOM checks; they do not establish business-level success.

Less output, more useful evidence

  • CLI and MCP responses remove repeated metadata, empty fields, and unnecessary geometry.
  • Accessibility outlines follow page order and filter unnamed structural nodes by default.
  • Batch results preserve successful evidence when some calls fail.
  • Parameter warnings suggest documented names and flag misplaced targeting fields.
  • Method discovery provides schemas and examples on demand.
  • Detailed health diagnostics are now opt-in through diagnostics: true or bbx doctor.

More agent integrations

Managed setup now includes Gemini CLI, Cline, Zed, Amp, Factory Droid, Pi, Kilo Code, Qwen Code, Goose, OpenHands, Muse Code, and Grok Build, alongside the existing integrations.

Generated MCP configurations launch the native binary directly. Installation repairs recognized global configurations that still reference removed v1 Node entrypoints, and diagnostics flag other missing launch paths.

Fixes

  • Improved iframe targeting, shadow DOM traversal, and screenshot geometry handling.
  • Corrected hidden-tab waits and navigation timing.
  • Preserved partial action progress and evidence during failures.
  • Tightened request lifetimes, inspection bounds, and content-script recovery.
  • Improved Windows native-host registration and executable path handling.

Breaking changes

  • The previous JavaScript runtime and BridgeClient API are no longer included. Integrations importing internal package files must move to the CLI, MCP, or authenticated wire protocol.
  • CLI shortcut, batch, and error output has changed. Update scripts that depend on removed metadata fields.
  • Routine health checks no longer include full diagnostics.
  • Unpacked extension development now requires a build into dist/ext.

Upgrading

Update both the extension and local runtime. Standalone installation is recommended:

macOS / Linux

curl -fsSL https://raw.githubusercontent.com/koltyakov/browser-bridge/main/scripts/install.sh | sh

Windows x64, PowerShell

irm https://raw.githubusercontent.com/koltyakov/browser-bridge/main/scripts/install.ps1 | iex

Then run bbx doctor and restart your agent or MCP client. Regenerate custom MCP configurations if they still point to old JavaScript entrypoints.

Installation guide · Changes since published v1.15.0

Assets 10
Loading