dsh-antibrow README

The project's README from github.com/antibrow/dsh-antibrow. As one markdown file: README.md.

dsh-antibrow

A DeepSeek Harness plugin that gives the agent a browser with an identity.

The browser is AntiBrow: a Chromium fork with fingerprint configuration at engine level, driven through the standard Playwright API. SDK docs are at antibrow.com/docs, and the dated detection measurements - including the checks that fail - are at antibrow.com/reports.

dsh plugin --profile <name> add dsh-antibrow

Why not a plain browser plugin

Every other browser plugin hands the agent a fresh Chromium. That is fine for reading a public page and useless for anything behind a login: the session dies with the process, the fingerprint is a stock automation build, and the traffic leaves from your machine.

A plain Playwright plugin dsh-antibrow
Identity between runs new browser every time one persistent profile per name
Logins gone when the process ends cookies and passkeys persist, optionally synced across machines
Fingerprint stock build, patched from page scripts spoofed inside the engine, before any page script runs
Egress your own IP residential proxy, with timezone, language and reported connection following its exit
Parallel identities one data directory to share one isolated profile per agent or per account
Tabs start from nothing last session restored, so the agent resumes where it stopped

The difference shows up the first time an agent has to be someone: check a mailbox, watch a dashboard, keep a marketplace account warm. A browser with no memory has to log in again on every run, and logging in again is exactly what a site treats as suspicious.

What it brings

The phone

{ "profile": "shop-mobile", "deviceType": "android", "temporary": true }

Android profiles are built from whole captured devices - the screen, the GPU report and the client hints agree with each other because they came off the same physical phone, and the plugin picks a row rather than assembling one. Three of them ship inside the package, so a free-tier agent can create an Android profile with no network round trip at all.

The device type is fixed when the profile is created and never drifts afterwards: a profile that was a phone stays that phone. Android needs engine 151 or newer - if none is available the launch fails rather than quietly handing you a desktop browser that claims to be a phone.

Measured

On a macOS host, through a US residential proxy, 2026-08-15, engine 151:

Check Result
whoer.net disguise 90%
creepjs headless signal 0%
creepjs stealth signal 0%
creepjs platform hints Arial, "Segoe UI" - no font from the host
Reported platform vs user agent agree (Win32 / Windows)
Timezone vs proxy exit agree (America/Los_Angeles)

The 10% whoer deducts is WebRTC, which had no route to a STUN server on that run. Reproduce all of it with tests/smoke - the harness is in this repository, and it fails loudly rather than printing a number nobody checks.

Install

dsh plugin --profile <name> add dsh-antibrow
export ANTI_DETECT_BROWSER_KEY=<key>
dsh --profile <name>

The tools
Sessions launch_browser close_browser list_sessions
Profiles list_profiles create_profile delete_profile
Proxies list_proxies claim_proxy
Page navigate click fill evaluate get_content screenshot
Live view start_live_view stop_live_view

launch_browser takes a profile name and creates it on first use. Pass temporary: true for automation work: those profiles are local-only and stay out of the desktop app's list, while still persisting on disk.

Before you rely on it

Configuration

The bundle inserts one row, mcp-antibrow, configuring the harness's MCP client against the anti-detect-browser CLI. Override it from your profile's own cordis.patch.yml by targeting that id - a patch replaces the row's whole config, so restate every key you keep:

- id: mcp-antibrow
  config:
    serverName: antibrow
    transport: stdio
    command: npx
    args: ['-y', 'anti-detect-browser@^2.19.1', '--mcp']
    env:
      ANTI_DETECT_BROWSER_KEY: !!js process.env.MY_OWN_VAR
      ANTI_DETECT_BROWSER_CACHE_DIR: /var/lib/antibrow

Turn it off without uninstalling:

- id: mcp-antibrow
  disabled: true

To run the SDK from a checkout instead of npm, use the overlay this package ships:

export ANTIBROW_SDK_CLI=<checkout>/dist/cli.js
dsh --profile <name> --patch node_modules/dsh-antibrow/cordis.patch.local.yml

Compatibility

Verified against dsh 0.1.0-rc.6 and anti-detect-browser 2.19.1, 2026-08-15. DeepSeek Harness is a developer preview and says it will break compatibility; this line is the claim, and it rots without a re-test.

The SDK version floor is real: 2.19.1 is the first release whose close path ends the browser process instead of only dropping the debugging connection. On an older one a closed session leaves the browser running, which keeps that profile's directory locked - the next launch of it dies before the debugging connection is ready - and holds a concurrency slot for the rest of the run.

License

MIT

dsh-antibrow (antibrow/dsh-antibrow)

web-automation
Searching Database…

11 ·GitHub
Dsh-antibrow
What is this?dsh-antibrow is a DeepSeek Harness plugin that gives an AI agent a persistent browser identity through AntiBrow, a Chromium fork with engine-level fingerprint spoofing. It exposes 16 MCP tools covering sessions, profiles, proxies and page control, driven via the standard Playwright API, with optional residential proxy egress.
Is this a browser plugin, or an actual browser?Both: AntiBrow is a real Chromium fork with fingerprint spoofing built into the engine itself, and dsh-antibrow is the DSH/MCP plugin that drives that browser through the standard Playwright API.
How do I install it and spin up my first browser profile?Install it as a DSH plugin via npm; the bundle inserts an mcp-antibrow row into the harness's MCP client config pointing at the anti-detect-browser CLI. Then calling launchbrowser with a profile name creates it on first use, downloading the engine (190-320MB) only on that very first launch.
Which DSH and SDK versions does it need?It is verified against DeepSeek Harness 0.1.0-rc.6 and anti-detect-browser SDK 2.19.1 or newer; 2.19.1 is required because it's the first release whose close path actually terminates the browser process instead of just dropping the debugging connection.
What's the catch with the free plan and running multiple agents?A free license key allows only one browser session at a time, counted per machine across every app sharing the engine, so parallel agents need a paid plan whose limit covers them. Also, two agents must never drive the same profile simultaneously — it's the same mistake as two people sharing one browser.
Which operating systems does it run on?Four builds across three operating systems: Windows, macOS and Linux, each for both x86-64 and arm64 — the same profile works unchanged on any of them.
Where are my logins and passkeys stored?Cookies and WebAuthn passkeys are stored inside the profile itself rather than the machine's OS keychain, so a passkey registered in one run still signs in on the next — and, with sync enabled, on another computer too.
What can I do with the Android device emulation?Passing deviceType: android when creating a profile turns it into a full Android device built from a real captured phone — touch points, mobile client hints, phone viewport and GPU all agree because they came off one machine. It requires engine 151 or newer, or the launch fails outright.
How well does it actually beat fingerprinting checks?In a dated 2026-08-15 test on macOS through a US residential proxy it scored 90% on whoer.net and 0% on CreepJS headless/stealth signals, with the missing 10% attributed to WebRTC having no STUN route on that run.
Is the unlimited free tier really unlimited?Yes — creating local profiles costs nothing and there's no cap on how many you keep. Only cross-machine profile syncing and the managed residential proxies are paid features.
Why not just use a plain Playwright automation plugin?A plain browser plugin hands the agent a fresh Chromium every run, so logins vanish, the fingerprint is a stock automation build, and traffic leaves from your own IP. dsh-antibrow keeps one persistent, spoofed profile per identity so sessions, fingerprint and proxy exit stay consistent across runs.
What are similar projects?invisible_playwright_mcp, Prism-Browser-Community, camofox-browser, browser-use, Seep-Reverse-Lab, dsh-reddit-radar, dsh-ios, dsh-android
Which topics is it in?anti-detect-browser, identity, stealth-browser, web-automation, mcp-tools, agent-tools, playwright, dsh, dsh-plugin, deepseek-harness, browser-automation, proxy
Creator
antibrow
Size
0.1 MB
Stars
11
Updated
CommitSep 12
Age
2mo
Commits · 90 Days