dsh-browser-use

Introduction¶

The plugin architecture of DeepSeek Harness (DSH) allows Agent Presets to mount external capabilities, thereby expanding the operational scope of agents. dsh-browser-use is a browser automation plugin for DeepSeek Harness. Through the existing Open Browser Use WebMCP ecosystem, it bridges browser control capabilities into DSH Agent Presets, addressing the needs of agents to execute tasks in Web environments.

Core Features¶

• MCP Server Connection: Connects the Open Browser Use stdio MCP server to a DeepSeek Harness Agent Preset.
• Tool Namespace: Exposes MCP tools through the stable mcp__open_browser_use__* namespace.
• Separation of Responsibilities: Does not reimplement WebMCP; Open Browser Use remains responsible for Chrome tabs, CDP, and page tool discovery.

Installation and Configuration¶

Before using this plugin, make sure the following environmental requirements are met:

1. Node.js Version: Node.js 22.19 or later, or Node.js 24 or later, is required.
2. Environment Dependencies: obu must be available in PATH, and the Chrome extension and Native Host must be connected to the target Chrome profile.

Install the Bundle to the Web Profile:

dsh plugin --profile web add github:mugnimaestra/dsh-browser-use

Create an authored Agent Preset based on the current standard preset, and add the following line to the configuration:

- id: browser-use
  name: dsh-browser-use
  config:
    failOnStartupError: true

Start a new Session and use this preset. If multiple Open Browser Use targets are installed, it is recommended to explicitly specify browser and profile in the configuration.

Usage and Limitations¶

In a Session, the Agent can invoke the following tools:

• mcp__open_browser_use__ping
• mcp__open_browser_use__user_tabs
• mcp__open_browser_use__call

Design Limitations

• Host Root Isolation: The Bundle patch is designed to be empty (cordis.patch.yml), with the goal of avoiding exposure of browser access permissions at the Host root level. This plugin should not be added to the Host root configuration, but should exist only within selected Agent Preset combinations.
• Session Ownership: A mounted plugin instance owns a long-running obu mcp subprocess. The current DSH Gate keeps this subprocess dedicated to the first live Agent that uses the mcp__open_browser_use__* tools. Another Session cannot use this process until the previous Session is destroyed.
• Security Boundary: This bridge does not add separate browser security policies. Authorization confirmation, licensing, and operational policies for production environments should belong to the Harness runtime or Host gateway. Page data from Open Browser Use is treated as untrusted input.

Ecosystem Links¶

• Plugin Directory
• GitHub Repository