bladebro

Give your AI agent a browser. Few tools. Full control. Real stealth. Zero runtime deps.

Re-render-immune refs · batch actions · auto-extract · self-improving · 6-layer stealth · drive your own browser

One MCP server · one CLI · one persistent page model · no Node.js · one binary · Linux · macOS · Windows

npm install -g bladebro && bladebro mcp

Demo · Install · The 5 tools · Usage · Your browser · Stealth Bench V1 · Stealth · Adapters · Comparison · Gotchas & limits

Bladebro is an agentic browser driver — it gives an AI agent full control of a real browser through 5 tools, not thirty. Built in Rust on a self-built CDP transport: one static binary, no Node.js, no Playwright, no runtime. It holds a persistent Live Page Model across tool calls, so every action returns what changed — never the whole page again.

⭐ New — drive your browser. bladebro rb on switches every surface to your own Chromium-family browser — your profile, your logins, your display — with the page-injection layer off entirely: a real environment has no manufactured tells to catch. Everything driver-side stays on. Real-browser mode →

🎬 Demo

Bladebro doing real work on two bot-protected sites — Reddit and X.com — in under two minutes. Real navigation, real actions, real content back: comment trees, threads and timelines as clean structured output.

https://github.com/user-attachments/assets/f67d80cc-a0ae-447a-8848-e35fce67f378

🏆 Stealth Bench V1

Run against browser-use's Stealth Bench V1: 80 real production sites protected by 11 anti-bot vendors. Bladebro cleared 68 (85%) — above every provider on the published leaderboard (browser-use-cloud: 81%).

• Out of the box — one IP, no proxy, no captcha solver, no fingerprint rotation, no cloud. Stock Chromium with Bladebro's stealth layer on by default.
• Honest run — real navigation of the real 80 sites; an open-model agent acted as the browsing agent because there was no paid cloud access, and the deviations are disclosed in full. The defensive layer being measured is Bladebro's own.
• Where it stands — perfect on Cloudflare (22/22) and reCaptcha (6/6); cleared the two sites browser-use-cloud did not (Shape, Temu); one named gap: Akamai (3/6).

Full report and methodology → · Per-site results (CSV)

✨ What makes it different

🚀 Install

npm (recommended)

npm install -g bladebro
bladebro mcp

Requires Chrome/Chromium; prebuilt Linux binaries require glibc 2.28 or newer. No Rust or compilation. npm resolves the prebuilt binary for your platform — zero postinstall scripts. Update later with npm update -g bladebro.

Every release builds and passes CI on Ubuntu, macOS and Windows. Linux ARM64 and macOS binaries are cross-compiled from Linux with cargo-zigbuild.

A Linux ENOENT launch error can mean the executable's loader is missing even when the file exists. The prebuilt binaries require glibc >=2.28; use a source build on Alpine/musl rather than reinstalling the same prebuild. A missing optional platform package is a separate error: reinstall with optional dependencies enabled.

Pi coding agent

pi install npm:bladebro

Registers 5 native tools (browser.act, browser.see, browser.state, browser.run, browser.vision) from the binary's own tools/list — tool definitions auto-adapt to any change, with zero extension maintenance.

DeepSeek Harness (DSH)

Add Bladebro as a native plugin in the Web UI's Plugins page, or run:

dsh plugin --profile web add bladebro

pnpm 11 defaults to a one-day release-age delay, so an unversioned install immediately after a release can select an older package. To select an exact release, append its version, for example dsh plugin --profile web add bladebro@4.6.7 (or enter bladebro@4.6.7 in Plugins). If your package manager explicitly enforces a stricter release-age policy, wait for its configured delay. Keep that policy intact.

Restart the profile and start a new chat. Desktop users can install bladebro from the same Plugins page. For terminal setup, enable Desktop's Manage dsh Command, fully quit the app, then use its bundled command:

dsh plugin --profile desktop add bladebro

Use Desktop's command for its profile; the npm DSH CLI cannot manage that app-owned profile. Open Desktop again after installation.

DSH discovers the five tools as mcp__bladebro__act, see, state, run and vision (each with the same prefix). Schemas and descriptions come from the binary; DSH handles permissions, image attachments, reconnection and cleanup through its native MCP bridge. DSH may also expose its own generic MCP resource helpers and choose PTC presentation. No API key, separate MCP configuration, global Bladebro install or extra plugin package is needed. Chrome/Chromium must be installed on the machine running the DSH host. A remotely hosted Web UI controls that host's browser, rather than the device viewing the UI.

Disable/re-enable the Bladebro bundle in Plugins, or remove it with dsh plugin --profile web remove bladebro (use desktop with Desktop's command). Restart the profile and begin a new chat after package changes. Other tools and settings remain intact. Do not also configure a second MCP server named bladebro; DSH refuses the duplicate namespace.

Updates use DSH's package manager: dsh plugin --profile web update bladebro, or Update in Plugins. The plugin and native binary travel in the same package, so ordinary Bladebro releases update both. Existing global/Pi installs are separate. No background downloader or installation scripts run.

Advanced configuration belongs in the profile's cordis.patch.yml:

- id: bladebro
  config:
    # Optional absolute source-build/portable executable; package binary is default.
    binaryPath: /absolute/path/to/bladebro
    env:
      CHROME_PATH: /absolute/path/to/chrome
      BLADE_HOME: /absolute/path/to/private/browser-data
    toolCallTimeoutMs: 180000

Windows YAML paths can use forward slashes, such as C:/Tools/bladebro.exe. The optional cwd and reconnect settings use DSH's native MCP configuration. The default per-call budget is 180 seconds; raise it for longer run sequences. Cancellation stops waiting, but an already-dispatched browser mutation may finish: observe its destination before trying it again.

The npm CLI keeps its Node.js >=14 requirement; the DSH plugin uses the host's Node.js requirement. Prebuilt binaries cover Linux x64/ARM64 (glibc >=2.28), macOS Intel/Apple Silicon and Windows x64. Other targets need a source build and binaryPath. See the official DSH plugin commands and Desktop command runtime.

Hermes Agent

npm install -g bladebro
bladebro hermes on

Requires a current Hermes CLI with config get --json --raw, config unset and mcp test; update Hermes if those commands are unavaila