Introduction

DeepSeek Harness (DSH) uses BrowserAuth by default for authentication in the Web Profile. Each time the service starts, you must extract the random Token from the generated URL and manually copy it into the browser to gain access. This adds extra steps for development debugging or everyday use. The dsh-skip-browser-auth plugin is designed to address this issue by automating the process to skip BrowserAuth, making Web access more direct.

Plugin Overview

This is a DSH client plugin maintained by iasiv5. It is adapted for the Web Profile, and its core feature is to automatically skip the BrowserAuth flow. Once installed and enabled, users only need to open the Web address to use it directly, without manually copying the Token.

Core Features

The plugin has the following characteristics:

  • Automatic BrowserAuth skip: Takes over the authentication logic and reduces manual operations.
  • Precise profile gating: Applies only to specific environments.
  • Strict paired matching: Requires the runtime and connection versions to match.
  • Version-generation adaptation: Adapts to the mechanisms of different DSH versions.
  • Non-invasive: Does not modify the DSH core or any underlying mechanism.
  • Web Profile only: Supports only the Web Profile and does not support Desktop.

Installation and Enablement

To install the plugin, the Web Profile must be specified. Run the following command to install it:

dsh plugin --profile web add @iasiv5/dsh-skip-browser-auth

If installing through the dsh-m plugin marketplace, you can search for it in the marketplace interface and operate directly. After installation, the DSH Web service must be restarted.

Usage

After installing the plugin and restarting the service, you can access the Web address directly, without copying the Token.

  1. Confirm DSH version compatibility (the runtime and connection must form a known version pair).
  2. Install the plugin.
  3. Restart DSH Web.
  4. Poll the Web address until a 200 status code is returned.

Cautions

There are security and compatibility limitations when using this plugin. Please note the following:

  • Trusted network limitation: After authentication is skipped, access from the local machine or within a trusted network no longer has an identity layer. Do not expose the DSH port to untrusted networks.
  • Desktop host dormancy: Desktop hosts are always automatically put into dormancy; this is by design.
  • Version matching: The runtime and connection must form a known version pair; mixed versions will cause the plugin to go dormant.
  • Mechanism modification: The plugin does not modify the DSH core or any mechanism, and official behavior can be fully restored after uninstallation.

Conclusion

The plugin automated Web Profile access through simple configuration, making it suitable for scenarios requiring frequent use of DSH Web. The related source code and detailed documentation are available on GitHub.