DeepSeek Harness (DSH) supports plugin-based extension. When developing agents for web automation, information extraction, or QA, developers often face a conflict between environment isolation and obtaining real browser state. dsh-tabbit is the official DSH plugin for Tabbit Browser, designed to address this pain point by providing a real browser execution environment.

What is This

This is an official DeepSeek Harness (dsh) plugin package maintained by Tabbit-Browser. It drives Tabbit in a code-first manner, enabling DSH to directly use real pages, login state, and interaction capabilities without relying on shell forwarding or headless browsers.

Core Capabilities

The plugin provides the following main features:

  • tabbit_browser: Users can use the real Tabbit built-in CLI mode to perform web page reading and page operations.
  • web_fetch: Redirects DSH’s web_fetch to Tabbit (supports JS rendering, login state, and system proxy).
  • @mention: In the dsh Web UI input box, type @ to list pages opened in the current session’s browser tasks and all tabs in the user’s browser; select one as context.
  • pageAccess permission: A separate page-read permission that requires user confirmation by default to protect data security.
  • tabbit_browser_install tool: Environment pre-check; detects the installed stable version of Tabbit and verifies the launcher and Runtime Service.
  • tabbit_plugin_update tool: Plugin update check; checks npm for the latest release at most once per day.
  • /tabbit-info command: Diagnoses plugin and host DSH versions, launcher, instance list, permission settings, and task usage.
  • tabbit skill: Informs the model of best practices for using Tabbit.

Installation and Enablement

Before installation, ensure the environment meets the following prerequisites:

  • Node ≥ 22.19
  • dsh ≥ 0.1.1-rc.2
  • Stable version of Tabbit Browser is installed and running (≥1.9.0)

Run the following command to install the plugin:

dsh plugin --profile web add dsh-tabbit

Configuration and Usage

Basic Configuration

Configuration items are located at dsh Settings → tabbit or $DSH_HOME/settings.yaml. Common configurations include:

  • tabbit.instance: Explicitly specifies a 16-character uppercase hexadecimal instance ID (can be listed via /tabbit-info).
  • tabbit.launcherPath: Auto-discovered by default, usually ~/.local/bin/tabbit-cli or the corresponding path on Windows.
  • tabbit.pageAccess: Permission policy; defaults to ask (ask once per session).
  • tabbit.intranetFetch: Policy for web_fetch access to intranet/loopback targets; defaults to ask.

Diagnostics and Tools

In the DSH input box, type /tabbit-info to view current diagnostic information, including plugin and host versions, launcher, instance list, active instance and its source, and permission settings.

Context Selection

In the dsh Web UI input box, type @ to list pages opened in the current session’s browser tasks and all tabs in the user’s browser. After selection, they can be used as context input.

Notes

  • Limitations: Mentions of Favorites/Bookmarks are not yet supported; using screenshots as context requires the current model route to support image input; the Windows version has limited regression testing.
  • Permissions: With user data security and login state in mind, an independent pageAccess permission is designed and requires user confirmation by default; the danger-full-access permission preset writes the approval policy never to the session, and this plugin will automatically allow it.
  • Dependencies: Prerequisites are Node ≥ 22.19 and dsh ≥ 0.1.1-rc.2.