Plugin directory / Developer / dsh-browser-bsk
dsh-browser-bsk
Verified · install-tested on dsh ylwl1997
What it does
Browser automation for DeepSeek Harness via bsk — navigate, snapshot, click, fill, and screenshot the user's real browser (with logins).
Works — verified, early-stage project
Browser automation for DeepSeek Harness via bsk — navigate, snapshot, click, fill, and screenshot the user's real browser (with logins). It installs cleanly and boots without issues in our testing. It's early-stage but functional.
“Verified” means our automated CI actually ran dsh plugin add in a clean profile and it booted — nothing more. Feature descriptions and version compatibility are the author’s claims. This is not a security audit and not an endorsement of third-party code.
README
dsh-browser
Browser automation for DeepSeek Harness via bsk 锟斤拷 lets your agent navigate, snapshot, click, fill, and screenshot the real Chromium browser (with your logins).
Install
dsh plugin add dsh-browser
Requires bsk on PATH + the browser-skill extension loaded (see browser-skill prerequisites).
Tools
| Tool | What it does |
|---|---|
browse_navigate |
Open a URL |
browse_snapshot |
Read the page as an accessibility tree (with @eN refs) |
browse_click |
Click an element by @eN ref or CSS selector |
browse_fill |
Type into an input |
browse_screenshot |
Capture a screenshot |
browse_observe |
Semantic VOM observation |
Example
Open https://example.com, read the page, and tell me the title.
License
MIT
Install
Install the catalog once, then DeepSeek Harness can find and install any plugin from this site automatically:
dsh plugin add dshbase-catalog Then say "install dsh-browser-bsk for me" — your agent finds it in the directory and installs it. Docs: dshbase-catalog · verified packs.
Web profile:
dsh plugin --profile web add dsh-browser-bsk Headless (CLI) profile:
dsh plugin --profile headless add dsh-browser-bsk Package
npm: dsh-browser-bsk · version 0.1.0 · tested on dsh 0.1.0-rc.6
Test report
Verified end-to-end: L1 install + L2 load + L3 runtime Q&A on dsh 0.1.0-rc.6.
When to use it
Extend the agent's coding surface — give it a new tool, workflow, or integration so it handles a dev task it couldn't before.
Who it's for
Developers who want dsh to behave like a teammate on real codebases — editing, running, and verifying changes rather than just answering.
For developers — extending it
The tool/command surface is the seam: expose more of the SDK, add smarter context wiring, or tighten the loop between code changes and verification.