antibrow/dsh-antibrow
dsh-antibrow
DeepSeek Harness plugin: give your agent a browser with a persistent identity - engine-level fingerprint spoofing, unlimited free local profiles, Android device emulation, passkeys that survive, and residential proxy egress.
Install
npx @deepseek-ai/dsh plugin --profile <name> add dsh-antibrowRestart `dsh web` after install. Bundle APIs can change during the developer preview.
README badge
[](https://dshhub.dev/plugins/dsh-antibrow)Paste this into your README. The star count updates with every catalog sync.
From the README
Excerpt from antibrow/dsh-antibrow, cleaned of badges and images.
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
…
