DeepSeek Harness Plugin

Tabbit-Browser/dsh-tabbit

Stars ★ 128 Downloads (30d) 2,752 Category Browser & Web Added 2026-08-21 npm dsh-tabbit

Gives DeepSeek Harness control of the Tabbit Browser: auto-loads the tabbit-browser skill on install, detects official Tabbit and Tabbit Browser releases (>= 1.9.0), checks the tabbit-cli persistent runtime, diagnoses the per-platform DSH sandbox mode needed to call the CLI, and downloads the region-matched official installer via a background job when no qualifying version is present.

Install

# from npm (prebuilt)

dsh plugin --profile web add dsh-tabbit

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

dsh plugin --profile web add github:Tabbit-Browser/dsh-tabbit

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

English | 简体中文 | Changelog

Tabbit Browser for DeepSeek Harness

A DeepSeek Harness (dsh) plugin bundle for Tabbit Browser. Through this plugin, dsh calls on Tabbit to complete agent tasks: real pages, real login state, real interactions, driven through a native code-first tool (not shell round-trips). Use it for web automation, information extraction, QA, and benchmarks.

What you get

Component Description
tabbit_browser Read and operate web pages using Tabbit's real, built-in CLI mode.
Browser-backed web_fetch Re-points dsh's web_fetch to Tabbit itself (dsh's built-in direct fetcher has no JS rendering, no login state, and bypasses the system proxy — under a fake-IP proxy setup it refuses every domain).
"Web tabs" @ mention Type @ in the dsh Web UI input box to list pages open in this session's browser tasks and every tab in the user's browser — pick one to add as context (contentless tab-group home pages are filtered out).
"Tab groups" @ mention Shown as its own section in the @ menu: find a whole tab group by name (or by any member page's title/URL). A group mention is a lightweight reference — the chip carries the member list and sending stays instant; the model pulls the pages it needs with tabbit_browser/web_fetch during the conversation (visible, permission-gated) instead of blocking the send on a full-group re-fetch.
Dedicated "page access" permission Full permission controls. Because dsh shares the user's cookies when it reaches Tabbit pages, it confirms pageAccess (asked once per session by default) and intranetFetch (per-request approval when web_fetch targets an intranet address).
tabbit_browser_install tool Environment preflight: detects an installed stable Tabbit build and verifies the launcher and Runtime Service; downloads Tabbit as a dsh background job when it's missing or outdated.
tabbit_plugin_update tool Plugin update check: asks npm for the latest release at most once a day, and silently installs a suitable version in the background.
tabbit skill Teaches the model best practices for using Tabbit. Defaults to Tabbit's own official skill at ~/.agents/skills/tabbit/ (it evolves with the browser runtime); this plugin bundles a fallback copy.

Installation

Prerequisites

  • A stable Tabbit Browser build (international edition or China edition, 1.9.0 or newer) that has been launched at least once (this registers the CLI launcher on first launch).
  • Node.js >=22.19 and dsh >=0.1.1-rc.2 (install dsh with npm install -g @deepseek-ai/dsh). On hosts below 0.1.2-alpha.1, the built-in web_fetch tool is unavailable in Web app sessions (tabbit_browser is unaffected).

Install dsh-tabbit

dsh plugin --profile web add dsh-tabbit                 # primary npm route

Other install methods

dsh plugin --profile web add github:Tabbit-Browser/dsh-tabbit # fallback when npm is unreachable
dsh plugin --profile web add link:/path/to/dsh-tabbit   # local development

This package supersedes the earlier tabbit-browser skill-only plugin, and continues on from the 0.2.x line published on npm — 0.2.x users get an upgrade notice from the daily update check, and simply re-running the install command upgrades in place.

Community & Support

Scan the QR code below to join the dsh-tabbit Developer Group to share feedback, ask questions, and discuss new features:

dsh-tabbit Developer Group

Settings

Basic configuration

DSH 0.2+: edit tabbit-browser in plugin settings, or add this to the profile's cordis.patch.yml:

- id: tabbit-browser
  config:
    instance: ""          # explicit 16-hex instance id; usually empty
    launcherPath: ""      # empty = discover tabbit-cli automatically
    pageAccess: ask       # ask (once per session) | always | never
    intranetFetch: ask    # intranet web_fetch: ask (once per session+origin) | always | never

On DSH 0.1.x, put the four fields under tabbit: in $DSH_HOME/settings.yaml. The plugin migrates those values on upgrade to 0.2; existing new settings take precedence.

Instance resolution priority

Priority order when this machine has more than one Tabbit build installed:

  1. an explicit tabbit.instance setting;
  2. the Tabbit instance currently viewing dsh-web (auto-detected: the client plugin pings /tabbit/instance-hint on page load, and the server traces the loopback socket's peer process up its parent chain to match the instance registry's browserPid; macOS only — naturally misses when a non-Tabbit browser has the page open) — "execute in whichever Tabbit you're viewing dsh in";
  3. an inherited TABBIT_PLAYWRIGHT_INSTANCE environment variable (the authoritative channel in the embedded form: Tabbit injects its own instance id when it launches its bundled dsh);
  4. automatic registry selection (the single online instance; an ambiguity error listing the candidates otherwise — on Windows, when the registry isn't readable, the native CLI picks for itself).

Full access note: dsh's danger-full-access permission preset writes the session's approval policy as never (dsh's definition: auto-deny every ask). This plugin's permission gate detects that override and auto-allows instead of issuing an ask that's guaranteed to be denied — full access means full access (bash is already unrestricted in that mode, so gating only the browser tool has no defensive value). Exception: a deployment-level default of never (not a session override) isn't visible to the public API and still gets denied — that combination gets a denial message pointing at the tabbit.pageAccess: always escape hatch.

Permissions & Security

  • Because the agent shares the user's real login state, pageAccess is a dedicated permission independent of filesystem/sandbox permissions, and asks for user confirmation by default.
  • Authorization is remembered: once a tool call succeeds, this session won't ask again; failures aren't recorded (a retry after failure asks again).

Development

Developing and testing this project depends on a local deepseek-harness checkout. The @deepseek-ai/* packages published on npm generally lag too far behind to install directly as dependencies, so you need to build a harness checkout locally first, then point the repo's .dsh-harness symlink at it with the script below (that path is already ignored in .gitignore). That's the only place you configure it — neither tsconfig.json nor package.json needs any changes.

Get and build deepseek-harness (skip if you already have one):

git clone https://github.com/deepseek-ai/deepseek-harness && cd deepseek-harness && pnpm install && pnpm build && cd ..

Point this repo at it — replace /path/to/deepseek-harness with your actual checkout path:

npm run link-harness -- /path/to/deepseek-harness   # or set DSH_HARNESS_PATH

Install and build:

pnpm install && pnpm build   # tsc → lib/
npm test                     # build + node --test tests/

Known limitations / Roadmap

  • Mentioning bookmarks/favorites isn't supported yet.
  • Screenshots entering context require a model route that accepts image input.
  • Windows regression testing is limited.

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.