DeepSeek Harness Plugin

Tencent/BrowserSkill#dsh-plugin-browserskill

Stars ★ 10563 Downloads (30d) 59,540 Category Browser & Web Added 2026-08-21 npm @wxg-prc-cpg/browser-skill-dsh-plugin

BrowserSkill bridge for controlling visible Chrome and Edge Agent Windows from DeepSeek Harness, with native browser tools, accessibility and VOM observations, screenshots, owned multi-session control, and a live Web UI overlay.

Install

# from npm (prebuilt)

dsh plugin --profile web add @wxg-prc-cpg/browser-skill-dsh-plugin

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:Tencent/BrowserSkill#path:/packages/dsh-plugin-browserskill

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

README

Lightweight DeepSeek Harness (dsh) plugin for BrowserSkill.

It packages the canonical browser-skill agent skill, automatically heals PATH for ~/.local/bin (and any configured bskPath), and bundles an on-demand bsk CLI + browser extension setup flow — running on the exact same bsk CLI, daemon (DSH_SESSION_ID session isolation), and Agent Window runtime as Claude Code, Codex, Cursor, and OpenClaw.

Installation

Add the plugin to your DeepSeek Harness profile (or install it from the DSH Web UI plugin panel), then start DSH:

dsh plugin --profile web add @wxg-prc-cpg/browser-skill-dsh-plugin
dsh --profile web

Replace web with your profile name if you use another profile. No separate bsk install-skill step is needed.

On-demand setup (first run)

If bsk and the browser extension are already installed, start using /browser-skill right away:

/browser-skill open https://example.com, summarize the page, and close the browser session.

If bsk is not installed on your computer yet, simply invoke /browser-skill (or ask DSH to open a webpage):

  1. The plugin detects that bsk is missing and instructs the DSH agent to run the bundled cross-platform installer (bin/install-bsk.mjs, which installs bsk into ~/.local/bin without sudo).
  2. Because the plugin automatically adds ~/.local/bin to the DSH host PATH, bsk becomes available immediately in the same session without restarting DSH.
  3. The agent runs bsk doctor and gives you the Chrome Web Store or Edge Add-ons link if the browser extension still needs to be installed and connected.

You can also run the bundled CLI installer manually at any time:

npx --package @wxg-prc-cpg/browser-skill-dsh-plugin bsk-dsh-install

Configuration

The plugin exposes one optional setting in cordis.patch.yml and the DSH Web UI settings form:

Option Default Description
bskPath "bsk" Path to the bsk executable or its directory. Defaults to resolving bsk from PATH or ~/.local/bin ($BSK_INSTALL_DIR).

How it works

  • Unified CLI runtime: Uses DSH's shell execution tool to run bsk commands (bsk open, bsk click, bsk fill, bsk sync, bsk close) with full support for shared control, full-page screenshots, structured extraction, file upload/download, task video recording, recipes, and website debugging.
  • Automatic session scoping: The bsk daemon recognizes DSH_SESSION_ID automatically so concurrent conversations and subagents keep isolated browser scopes without manual --session flags.
  • MCP alternative: For restricted profiles without shell execution, connect bsk mcp through @deepseek-ai/dsh-mcp-client instead (see MCP setup).

Updating

Update the plugin in your DSH profile, then restart that profile:

dsh plugin --profile web update @wxg-prc-cpg/browser-skill-dsh-plugin --latest

Update the bsk CLI (bsk update --yes) and browser extension separately when a release requires a newer protocol version.

Content from the project README on GitHub ↗

Links

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.