AI Agent Hub
Back to plugins
dsh-browser-slotpool preview

dsh-browser-slotpool

Workflow Updated 2026.09.03

Run the following command in DeepSeek Harness:

dsh plugin install bluechips-zhao/dsh-browser-slotpool

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

Run dsh plugin install bluechips-zhao/dsh-browser-slotpool inside DeepSeek Harness to install this plugin; the source repository is available at https://github.com/bluechips-zhao/dsh-browser-slotpool—restart the target profile after installation.

About this plugin

Running multiple browser sessions side by side in DeepSeek Harness often means port collisions, memory blow-ups, and one profile silently killing another Chromium. dsh-browser-slotpool replaces that chaos with a fixed-size CDP port slot table (default 9222, 9223): first come first served, and when the pool is full it refuses cleanly and prints who holds each slot. Every mcp-client session owns exactly one slot, and browser tools appear to the model under the mcp__browser__ prefix.

Under the hood it nails four failure-prone areas: atomic locking via O_EXCL exclusive file creation eliminates races; PID liveness checks with stale-lock reclamation free a slot the instant its owner dies; idempotent readiness probes skip spawning if the port is already up and never kill another slot's browser; and stdio is fully delegated to Playwright MCP while diagnostics stay on stderr, keeping the MCP protocol channel clean.

Ideal for DSH users juggling multiple profiles or concurrent sessions, and for automation developers who need a predictable, self-healing browser MCP. It ships as a pure .mjs launcher plus one patch-layer bundle line—no build step, no TypeScript, no extra dependencies beyond what DSH already provides.

Screenshots

Use Cases

  • Run parallel browser automation across profiles without port conflicts
  • Auto-reclaim a slot when a browser process crashes—no manual cleanup needed
  • Reject new sessions when the pool is full and print slot holders instead of hanging

Best For

  • DSH users running multiple concurrent profiles or sessions
  • Automation developers who need a predictable, self-healing browser MCP
  • Workflow orchestrators who want to eliminate browser resource contention