dsh-browser: A Real Browser for Every DeepSeek Harness Conversation

What Does It Do?

CJYLZS/dsh-browser is a DSH plugin for DeepSeek Harness that gives every conversation its own real local browser. It solves the problem of an agent that can only read text and cannot actually operate a web page: Chrome or Edge runs as a separate process with its own profile and its own CDP port, the agent drives it through six tools, and the right sidebar mirrors the same pages. Nothing is shared between conversations — not tabs, not cookies, not the port — and closing the harness does not leave behind a browser pretending to be part of the app.

Core Features

• One browser per conversation: the sidebar pane names its session on the socket it connects with, and a tool call resolves its browser from the session the call came from, so two conversations cannot see each other's tabs or sign-ins.
• Trusted input in both directions: clicks and typing in the sidebar are forwarded to the real page, and the agent's click and type tools dispatch real mouse and text events at the element's own position, which sites that ignore synthetic clicks still accept.
• Attachable: each browser listens on an external CDP port, so the built-in inspector, another Playwright instance, or the bundled script can attach to the same browser the sidebar is mirroring.
• Readable without selectors: the snapshot tool prints the page's accessibility tree with a ref for each node, which is how the agent reads a page it has never seen and names an element to click.
• A small tool set that leans on code: six tools rather than forty, with the general-purpose evaluate tool doing most of the work and the rest covering what code cannot express.

How to Use This Plugin?

In a conversation's right sidebar, pick New tab → Browser; that session's browser starts and its picture appears, the address bar navigates on Enter, and clicking, scrolling, and typing over the picture go to the real page. Then just ask for something in plain language, for example to open the docs and say what the install section contains — the tools act on the same browser the pane shows, so you watch the work happen. When you want your own tools, the inspector, another Playwright instance, or the bundled script can attach to the same browser. Closing the tab does not stop the browser; reopen it and the same pages are there, while stopping one is an explicit action in the pane's status row. A Chrome or Edge installation is required, since the Playwright core dependency downloads no browser of its own.

How to Troubleshoot This Plugin?

If the browser will not start, first confirm that Chrome or Edge is installed locally, because the Playwright core dependency ships no browser of its own. If the sidebar picture is blank or tools seem to act on a different page, check whether that conversation's browser was explicitly stopped and reopen the tab. If an external tool cannot attach, make sure the browser's CDP port is not taken by another process, and follow the official notes on known limitations and deferred work.