A README-backed DSH plugin for browser sessions that keep identity, cookies, passkeys, and the last session between runs.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-09-13
License
MIT
01What can it help you accomplish?
Run a DeepSeek Harness agent with a persistent browser identity
A Playwright-driven AntiBrow browser with a named profile, persistent cookies and passkeys, and optional proxy egress
DSH users who need an agent to resume logged-in browser work across runs
Automate logged-in pages, dashboards, and account workflows from DSH
Browser sessions with navigation, click, fill, evaluate, content, screenshot, profile, proxy, and live-view tools
Developers running browser automation through DeepSeek Harness and the MCP tool surface
02How to install into DeepSeek Harness
Prerequisites
- A DeepSeek Harness profile name to pass to the documented dsh commands
- An AntiBrow license key exported as `ANTI_DETECT_BROWSER_KEY`
Installation steps
- 01
Install the plugin with `dsh plugin --profile <name> add dsh-antibrow`
$ dsh plugin --profile <name> add dsh-antibrow
- 02
Export the license key with `export ANTI_DETECT_BROWSER_KEY=<key>`
- 03
Start the profile with `dsh --profile <name>`
$ dsh --profile <name>
Verify the integration
Not specified by the author
03DSH integration and capability boundaries
README-documented DeepSeek Harness plugin with bundled MCP configuration
Persistent named profiles
A profile name passed to `launch_browser`→One isolated browser profile per name, with the last session restored
Profile data persists on disk and should not be shared by concurrent agentsEngine-level fingerprint configuration
A browser profile and its AntiBrow engine→Engine-level user agent, platform, screen, fonts, canvas, WebGL, and audio answers
Android device emulation
A profile created with `deviceType: 'android'`→Touch points, mobile client hints, phone viewport, and phone GPU behavior
Android profiles require engine 151 or newerBrowser automation and live view
An MCP browser session→Session, profile, proxy, page-control, and live-view operations
Residential proxy egress
A configured proxy claim→Residential proxy egress with timezone, language, and reported connection following the exit
Managed residential proxies are paid parts of the servicePortable profile export
A local browser profile→An exported profile file that can be imported on another machine
Unsynced profiles remain local to the desktop app and disk
04Who is it for? When not to use it?
Good for
- DSH users who need an agent to resume logged-in browser work across runs
- Developers running browser automation through DeepSeek Harness and the MCP tool surface
Not for
- A free key allows one browser at a time; extra parallel launches are refused when the plan limit is exceeded.
- The engine downloads 190-320 MB on first launch into a shared cache directory.
- Two agents should not drive one persistent profile at once; the last one to close wins.
05Compatibility, maintenance and safety notes
- A free key allows one browser at a time; extra parallel launches are refused when the plan limit is exceeded.
- The engine downloads 190-320 MB on first launch into a shared cache directory.
- Two agents should not drive one persistent profile at once; the last one to close wins.
- The project documents four builds across Windows, macOS, and Linux on x86_64 and arm64.
MIT; README-backed project with no release listed in the facts pack
06Frequently asked questions
How do I install dsh-antibrow in DeepSeek Harness?
Run `dsh plugin --profile <name> add dsh-antibrow`, export `ANTI_DETECT_BROWSER_KEY`, then start the profile with `dsh --profile <name>`. The README does not specify a separate verification command.
How does dsh-antibrow connect to DSH?
The repository describes dsh-antibrow as a DeepSeek Harness plugin. Its bundle adds an `mcp-antibrow` row that configures the harness MCP client for the `anti-detect-browser` CLI.
What persists between DeepSeek Harness runs?
A named profile persists on disk, with cookies and passkeys retained; the README also says the last session can be restored. Use separate profiles for separate agents or accounts.
Can a DSH agent use an Android browser profile?
Yes. Create the profile with `deviceType: 'android'`. The README says Android needs engine 151 or newer and fails launch when that engine is unavailable.
What should I watch before running parallel DSH sessions?
A free key permits one browser at a time, and two agents should not drive one persistent profile concurrently. The first launch also downloads 190-320 MB depending on platform.
07Related DSH workflows
ruflo
by ruvnet
🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
reactive-resume
by reactive-resume
A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
everos
by evermind-ai
One portable memory layer for every AI agent: local-first, Markdown-native, user-owned, and self-evolving across apps, tools, and workflows.
yao
by yaoapp
✨ All your agents and workspaces in one place, on every device you own. Track tasks on a board, accessible from desktop, mobile, browser, or API. Self-hosted.
08Data and sources
A [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) plugin that gives the agent a browser with an iden…
The bundle inserts one row, `mcp-antibrow`, configuring the harness's MCP client against the `anti-detect-browser` CLI.
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-09-13. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.