Integrate Tabbit browser automation into DeepSeek Harness, automatically detecting browser version and runtime, and downloading compatible installation packages in the background when missing.
Install
$ dsh plugin --profile web add github:Tabbit-Browser/dsh-pluginRun the command above in your terminal to install this plugin via the dsh CLI. You can switch Profile in the top-right corner. New to dsh? Read the beginner tutorial
One-Sentence Positioning
A DSH package branded as "Tabbit Browser" in the DSH plugin marketplace that equips DeepSeek Harness with a Skill capable of controlling the local Tabbit browser for automation operations, and automatically downloads the installer when the browser is missing or using an outdated version.
Core Capabilities
- Register a bundled Skill named
tabbit-browserin DSH, enabling the model to invoke it via/tabbit-browserorskill({ name: "tabbit-browser" }) - Provide
tabbit_browser_installtool to automatically check whether a stable Tabbit version 1.9.0 or higher is installed on the local machine - Detect
tabbit-clidaemon runtime and Playwright Runtime processes (browser-runtime-service.mjs/nodejs-playwright-runtime.mjs) - Cache detection results per agent session to reduce redundant detection overhead; use
refresh: trueto actively invalidate and re-detect - When the browser is missing or the version doesn't match, download the appropriate regional and architecture installer to the
Downloadsdirectory via DSH background tasks - Automatically select download source based on system locale (tabbit.com for Mainland China, tabbit.ai for other regions), and verify file format (exe/dmg)
Technical Implementation
- Language: JavaScript (ESM)
- Key Dependencies:
@deepseek-ai/cordis,@deepseek-ai/dsh-tools,@deepseek-ai/dsh-jobs,@deepseek-ai/dsh-skill - Architecture Pattern: DSH bundle package + Cordis patch injection; declare
inject: ['skills', 'tools', 'jobs'], inject Skill Provider viacordis.patch.ymlat host startup, and register bundled Skill and detection tool viaapply(ctx) - Entry Files:
index.js(main entry) +installer.js(environment detection and installer download implementation)
Use Cases
When users want AI agents to directly operate the local browser for web interaction, data extraction, automation testing, or evaluation tasks, this plugin exposes the Tabbit browser as a controlled Playwright runtime to the DSH model. It fits the bridging scenario where "the agent runs in sandbox, the browser runs on host GUI"; when users haven't manually installed Tabbit, the plugin can also handle the download phase for them.
Prerequisites and Compatibility
| Dependency | Minimum Version | Description |
|---|---|---|
| DSH Host | dsh CLI | Must be able to run in an environment where dsh --version executes |
| Cordis | >=4.0.0 | Internal DSH dependency, provides Skill/Tool/Job registration capability |
@deepseek-ai/dsh-jobs | >=0.1.0-rc.5 | Background task support, this plugin starts downloads via ctx.jobs.start |
@deepseek-ai/dsh-tools | >=0.1.0-rc.5 | Tool registration framework |
@deepseek-ai/dsh-skill | >=0.1.0-rc.5 | Skill Provider registration framework |
| Node.js | >=20 | Declared by package.json#engines.node |
| Platform | macOS (arm64/x64) / Windows x64 | Linux is not in the installer list; source code will throw errors |
Installation
dsh plugin --profile web add github:Tabbit-Browser/dsh-plugin
Configuration Options
| Config | Type | Description | Default |
|---|---|---|---|
tabbit_browser_install.refresh | boolean | Force re-run browser and runtime detection, discarding current session cache. Only use when Runtime/launcher errors occur or browser is updated/restarted | false |
This plugin has no DSH global configuration items; all adjustable parameters are passed as arguments when calling the tool.
FAQ
Q: Do I need to manually install Tabbit browser before using it?
A: Not required. The plugin first tries to detect whether Tabbit stable version 1.9.0 or higher is already installed on the system; if not, it automatically starts a background task to download the appropriate regional and architecture installer to the Downloads directory for the user to manually complete the native installation.
Q: Which operating systems are supported?
A: Only macOS (Apple Silicon and Intel) and Windows 64-bit. The source code only declares installer specifications for these three platform/arch combinations; Linux will error out due to not finding matching download configuration.
Q: Do I need to separately install tabbit-browser Skill after installing the plugin?
A: No. The plugin comes with a bundled Skill pre-installed; skill-tabbit-browser is inserted into the DSH host via cordis.patch.yml, and the Skill becomes visible after DSH starts.
Q: Will detection results run every time?
A: No. Successful detection results are cached in WeakMap per agent session; subsequent calls directly return cached: true. Only when Runtime/launcher fails or the browser changes, passing refresh: true will invalidate and re-run.
Q: What happens if multiple downloads run simultaneously in the same agent?
A: The plugin tracks in-progress jobs; repeated calls will return the existing jobId and prompt "a download is already in progress", preventing concurrent download tasks.
Q: How to troubleshoot CLI connection failure on Windows (BROWSER_RUNTIME_UNAVAILABLE)?
A: The plugin doesn't proactively request Full Permission. First normally call tabbit-cli tasks for connection probing; if the browser, launcher, and Runtime processes are all detected but this error persists, ask the user to switch the current DSH session to Full Permission and stop the current task, don't retry or switch browsers.
Q: What's the difference between installers downloaded by Mainland China and overseas users?
A: The plugin reads the system locale: Mainland China CN downloads the domestic version from tabbit.com ("Tabbit Browser", bundleId com.tab-browser.Tabbit), other or unknown locales download the international version from tabbit.ai ("Tabbit", bundleId com.tabbit-ai.Tabbit). Both versions are supported, but the display name and bundleId differ.
Q: How to uninstall?
A: Use dsh plugin --profile web remove github:Tabbit-Browser/dsh-plugin. The plugin doesn't modify persistent data outside the system; detection cache only exists in the current DSH agent session memory and becomes invalid upon restart.
Difficulty Level
Beginner — The installation command is a single line, and the plugin automatically handles Skill registration and browser detection; you only need to read the README's "Prerequisites" and "Scope" sections when troubleshooting Runtime connection or download failures.
Known Issues and Limitations
- Does not recognize dev builds: Only detects stable
TabbitandTabbit Browser; dev builds are ignored (installer.js hardcodeschannel: 'stable') - Does not auto-launch installer: After download completes, it only tells the user the path; the user must manually double-click
.dmg/.exe; the plugin won't open it (README.md:67 explicitly states) - Won't replace or supplement native browser tools: This plugin only exposes
tabbit_browser_install; it doesn't provide tools liketabbit_browser_evaluatefor direct browser invocation (README.md:96 explicitly states) - Windows sandbox mode limited: DSH's
read-onlyandworkspace-writemodes on Windows use restricted tokens and cannot write to Runtime named pipes; only when Browser, launcher, and Runtime are all detected but CLI connection fails, prompt the user to switch to Full Permission and stop the task, don't retry - Linux not supported:
installer.jsonly defines three platform/arch combinations for macOS and Windows; Linux is neither in the detection scope nor has available download sources (installer.js:113-140) - Multiple Tabbit instances will prompt ambiguity without error: If multiple Tabbit instances are running, detection results will mark
playwrightRuntimeAmbiguous: trueand prompt setting theTABBIT_PLAYWRIGHT_INSTANCEenvironment variable, rather than misidentifying as Runtime not running
这是一个 Tabbit 浏览器为 Deepseek Harness 提供的一个 plugins。你可以在 Deepseek Harness 中安装这个插件，给 Deepseek Harness 提供控制 Tabbit 浏览器的能力。
安装与启动
1. 检查并安装 DeepSeek Harness
先检查本地是否已经安装 DSH：
dsh --version
如果命令能够正常输出版本号，直接进入下一步。如果提示找不到命令，请根据操作系统安装。
macOS
安装 Node.js 20 或更高版本，然后安装 DSH：
brew install node
npm install -g @deepseek-ai/dsh
Windows
在 PowerShell 中安装 Node.js LTS：
winget install OpenJS.NodeJS.LTS
安装完成后重新打开 PowerShell，再安装 DSH：
npm install -g @deepseek-ai/dsh
安装后再次运行 dsh --version，确认 DSH 可以正常使用。
2. 安装 tabbit-browser 插件
dsh plugin --profile web add github:Tabbit-Browser/dsh-plugin
3. 启动 DSH
dsh web
安装插件后，bundle 会自动加载 Skill Provider，模型可通过
skill({ name: "tabbit-browser" }) 或 /tabbit-browser 加载说明。Skill 会检查国内或
国际正式版、要求至少一个版本达到 1.9.0，并检查 tabbit-cli 常驻运行时。
没有安装或版本过低时，模型会直接创建 DSH 后台任务：macOS 读取系统地区，Windows
调用系统地区 API；中国大陆下载国内正式版，其他地区或无法识别地区时下载国际正式版。
安装包会保存到用户的 Downloads 目录，任务完成后 DSH 会通知安装包路径。
前提
- 必须安装
1.9.0或更高版本的正式版 Tabbit 浏览器。国际版Tabbit和国内版Tabbit Browser均支持，安装任意一个即可。 - 当前 DSH profile 已提供
ctx.skills、ctx.tools、ctx.jobs以及对应模型工具。 dsh-tool-jobs已为当前 Agent 提供后台任务控制和完成通知。- 当前 DSH profile 已提供运行在 Tabbit Browser 所在宿主机的 Bash/Shell 工具。
- Shell 的执行环境可以访问 Browser-owned Runtime Service。
- Windows 上 DSH 的
read-only与workspace-write限制令牌无法写入 Runtime 命名管道。Skill 先正常执行tabbit-cli tasks连接探测；成功时完全不询问 权限。仅当 Browser、launcher 和 Runtime 进程均已检测到但连接返回BROWSER_RUNTIME_UNAVAILABLE时，才要求用户把当前 DSH 会话切换到 Full Permission，并立即停止当前任务，不重试或继续浏览器操作。
范围
本包负责：
- 随插件安装自动发现和加载
tabbit-browserSkill，无需单独安装 Skill。 - 检测国际正式版
Tabbit和国内正式版Tabbit Browser。 - 要求任一正式版版本不低于
1.9.0。 - 检查
tabbit-cli常驻运行时；未运行时提醒用户重启一次 Tabbit。 - 多个 Tabbit 实例同时运行时，仍判定 Runtime 可用；模型需根据 CLI 提示设置
TABBIT_PLAYWRIGHT_INSTANCE，不会把实例选择歧义误报为 Runtime 未运行。 - 诊断当前平台调用 CLI 所需的 DSH sandbox mode；Windows 返回
cliSandboxMode: danger-full-access，其他平台返回default。 - 按 Agent session 缓存成功的环境检查；仅在 Runtime/launcher 失败或安装变化后
通过
refresh: true主动失效并重新检查。 - 在两者均未安装或所有正式版版本过低时，通过
ctx.jobs后台下载适配系统地区的正式版安装包。 - 中国大陆使用
tabbit.com国内版下载源，其他地区使用tabbit.ai国际版下载源。 - 输出下载进度，完成后通知安装包绝对路径。
它不会检测开发版，不会自动打开 .dmg 或 .exe，也不提供
tabbit_browser_evaluate 等原生浏览器工具。
如果 DSH 的 Bash 运行在 E2B、远程容器或无法访问本机 GUI Browser 的沙箱中，本 Skill 不会使 Tabbit 自动化变得可用。
开发验证
npm test
npm pack --dry-run