gemone/dsh-chrome
DeepSeek Harness plugin: model-facing Chrome DevTools Protocol (CDP) tools — navigate, evaluate, screenshot, s
Gives the agent model-facing tools that drive a local Chrome over the DevTools protocol. The README's tool table maps each tool to the underlying browser primitive — e.g. chrome_screenshot captures a screenshot and returns it as an image block (requiring an image-capable model) via Page.captureScreenshot. It documents the launch architecture (launcher.ts handles executable discovery, Chrome spawn and /json/version polling), a configuration example for the profile patch, the option to connect to an already-running Chrome, a security section, and requirements plus a development workflow.
Install
dsh plugin --profile web add github:gemone/dsh-chromeREADME install, from-GitHub route quoted verbatim: dsh plugin --profile web add github:gemone/dsh-chrome. The npm name dsh-chrome resolves to 0.1.3 but its registry repository field points to github.com/stuarthu/dsh-chrome — a different owner — so no npm claim is made here (registry-verified 2026-09-12). The README also documents a local-checkout route (cd dsh-chrome && pnpm install && pnpm build && cd .. then dsh plugin --profile web add ./dsh-chrome), a tarball route (./dsh-chrome-0.1.0.tgz), removal with dsh plugin --profile web remove dsh-chrome, and connecting to an already-running Chrome.
Compatibility
DeepSeek Harness web profile with a local Chrome/Chromium install. The README documents a launcher that finds the executable, spawns Chrome and polls /json/version, plus a configuration row in the profile's cordis.patch.yml; the README notes config edits hot-apply because DSH watches the file transactionally. chrome_screenshot requires an image-capable model; the README also warns that connecting to an already-running Chrome has security implications.
Details
- Repo: gemone/dsh-chrome
- Category: Other
- Stars: 2
- Version: GitHub/source install (npm name dsh-chrome 0.1.3 exists but belongs to a different repository per its registry field, so it is not claimed)
- Last push: 2026-08-13
- First seen: 2026-08-13
Recent updates
The README documents the tool surface, launch architecture and configuration rather than a versioned changelog: the launcher discovers the executable and polls /json/version, config lives in the profile patch (cordis.patch.yml) and hot-applies, and the security section covers the implications of attaching to an already-running Chrome. It also notes chrome_screenshot needs an image-capable model.
FAQ
- How do I install dsh-chrome?
- dsh plugin --profile web add github:gemone/dsh-chrome — the README's GitHub route. A local checkout needs pnpm install && pnpm build first, then add the directory; a tarball route is also documented.
- Which tools does it add?
- Model-facing tools that drive the browser over the DevTools protocol; the README's table names each one and its primitive, including chrome_screenshot (requires an image-capable model).
- Can it attach to my existing Chrome?
- Yes — the README documents connecting to an already-running Chrome, with a security section discussing the implications. Configuration in cordis.patch.yml hot-applies.
Alternatives
deepseek-ai/deepseek-harness · awesome-dsh-plugin/awesome-dsh-plugin · yjh051108/dsh-routing-suite