Introduction

In DeepSeek Harness (DSH) development scenarios, WSL environments are commonly used to run local services or documentation sites. Developers need to view these services from the Windows side (for example, http://127.0.0.1:3080). Opening a browser directly inside WSL usually cannot access the Windows-side interface, while manually copying the URL into a Windows browser adds operational overhead. The dsh-wsl-browser plugin provides the win_open_url tool, aiming to solve the handoff problem between WSL and Windows browsers.

Plugin Description

This plugin belongs to the dsh-wsl-kit suite. It works by starting from the WSL environment and using the win_open_url tool command to open the specified http/https URL in the default Windows browser. Note that this plugin only triggers the browser to open from the WSL process; it does not fetch page content inside WSL.

Installation

First, install the plugin:

dsh plugin --profile web add github:173787247/dsh-wsl-browser

Configuration

If you need to adjust parameters such as the timeout, add the following to the configuration file:

- id: dsh-wsl-browser
  name: dsh-wsl-browser
  config:
    timeoutMs: 15000

Usage

The tool accepts one required parameter: url.

  1. Call win_open_url in the WSL environment.
  2. Pass a URL that starts with http:// or https://.

For example, if you have started a local service at http://127.0.0.1:3080 in WSL, you can invoke it directly:

win_open_url http://127.0.0.1:3080

Notes

  • Only the http and https protocols are supported; the file: protocol is not supported.
  • If localhost port forwarding fails, the result may include a hint based on the current WSL IP. It is recommended to troubleshoot with the dsh-wsl-port plugin.
  • This plugin does not include configuration for Cloud Flash models.

Ecosystem Context

The design philosophy of DeepSeek Harness is “everything is a plugin.” dsh-wsl-browser is a community-maintained tool intended to provide convenience for local development. Its directory and GitHub repository are independently maintained projects and have no direct ownership relationship with official DeepSeek applications.