AI Agent Hub
Back to plugins
🧰

dsh-antibrow

Web Tools Updated 2026.08.25

Run the following command in DeepSeek Harness:

dsh plugin install antibrow/dsh-antibrow

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install antibrow/dsh-antibrow in the DeepSeek Harness terminal to install this plugin; the source repository is https://github.com/antibrow/dsh-antibrow .

About this plugin

A plain Playwright plugin hands the agent a throwaway browser. The moment the process exits, every login vanishes, the fingerprint is a stock automation build, and traffic leaves from your own IP. The first time an agent needs to be someone, whether checking a mailbox, watching a dashboard, or keeping a marketplace account warm, a browser with no memory must log in again on every run, and repeated logins are exactly what sites flag as suspicious. dsh-antibrow solves this by giving the agent a browser with a persistent identity that survives across runs.

Its core capabilities center on coherence. The engine answers user-agent, platform, screen, fonts, canvas, WebGL, and audio probes before any page script executes, so there is no injected script for a detector to find. Timezone, locale, and reported network profile are derived from the residential proxy real exit, keeping the story internally consistent. Cookies and passkeys persist with the profile and can sync across machines. The free tier offers unlimited local profiles stored on disk with no cap on count. Sixteen MCP tools cover sessions, profiles, proxies, page control, and a live dashboard view. A single parameter, deviceType set to android, turns the agent into a phone with touch input, mobile viewport, and a matching GPU report.

Ideal for teams whose agents must operate logged-in sites long-term: e-commerce competitor monitoring, multi-account marketplace upkeep, SaaS dashboard auditing, and email automation. For teams running parallel agents, each gets its own isolated profile so sessions never collide. Developers who want to bridge the agent browser and a human desktop browser can export, import, and open the same profile in either context, keeping one coherent identity.

Use Cases

  • Agent stays logged in on e-commerce sites to monitor competitor pricing and stock
  • Multiple agents maintain separate marketplace accounts in parallel without collision
  • Access mobile-only web features by switching to an Android phone profile

Best For

  • Web automation teams that need agents operating logged-in sites
  • E-commerce and marketplace operators running multi-account parallel strategies
  • Developers who want the agent browser and a human desktop browser to share one identity