Introduction

When using an Agent to operate a browser in DSH, it is usually not just about calling tools, but also about clarifying which operations are allowed, which require local confirmation, and where credentials are stored. @puxora/dsh-browserpilot is the standalone DSH cross-platform plugin for BrowserPilot: The Host side provides BrowserPilot MCP tools to the Agent, while the Web side provides a dedicated settings entry, permission policies, and a management panel button.

What is this

It is @puxora/dsh-browserpilot, maintained by Puxora, with an MIT license.

It solves the problem of DSH Agents connecting to local Chrome: The Host side provides MCP tools, and the Web side provides settings, permission policies, and management panel entries.

This plugin does not save tokens, cookies, or browser credentials to DSH.

Core Features

  • Local Chrome Control: Enables DSH Agents to use local Chrome via BrowserPilot.
  • Tiered Permissions: Implements tiered restrictions on browser operations; DSH local policies can only further restrict, not relax, BrowserPilot global policies.
  • Local Final Confirmation: Retains the local final confirmation step.
  • Connection Diagnostics: Call browserpilot_status to view connection status.
  • Management Panel Entry: Opens the local management panel from DSH settings.

Installation and Enablement

1. Prepare BrowserPilot Local Bridge

First, register the current Windows user’s Chrome Native Messaging Host:

browserpilot install

The command output will provide the chrome-extension directory; the next step is to load this directory in Chrome.

In Chrome Developer Mode, load the chrome-extension directory output by browserpilot install.

Start and check status:

browserpilot start
browserpilot status

2. Install DSH Plugin

Execute:

dsh plugin --profile web add @puxora/dsh-browserpilot@latest

If installing locally for development, replace the example path G:/github/dsh-browserpilot in the command with your local repository path.

Typical Usage

  1. Open Settings → BrowserPilot and confirm that Browser Tools are enabled.

  2. Call browserpilot_status in DSH.

  3. Once the status is connected, use browser tools starting with mcp__browserpilot__.

Settings and Permissions

  • This plugin does not save tokens, cookies, or browser credentials to DSH.
  • DSH local policies can only further restrict, not relax, BrowserPilot global policies.
  • Sensitive operations are prohibited within DSH, including upload, download, script, and Cookie or credential-related operations.
  • The plugin synchronizes global values every 3 seconds; when the daemon is unavailable, global controls will become read-only.
  • The default connection handshake timeout is 12 seconds, and the default timeout for a single tool call is 60 seconds.

Management Panel

The management panel button in the Settings page opens:

http://127.0.0.1:9876/

Applicable Scenarios and Notes

Suitable for DSH / Agent developers: Need to let Agents operate local Chrome within DSH while retaining local confirmation and sensitive operation restrictions.

Note: This plugin runs with the permissions of the current DSH process. You should check the source code and license before installing.

Source Code Repository: https://github.com/Puxora/dsh-browserpilot.

License: MIT.

Links

GitHub: https://github.com/Puxora/dsh-browserpilot