Preface¶

When developing in DSH, I often encounter a scenario: the Agent at hand uses an API identity, but some tasks are better handled by switching to the web version—for example, wanting to use the quota and sessions from the web account. Minimizing the window, reopening the browser, and logging in again every time is very inefficient. If there were a fixed entry in the client, clicking it could expand the built-in browser to open chat.deepseek.com, or directly invoke the system browser to reuse an existing login, saving many steps.

dsh-deepseek-web-entry is a plugin for this purpose: it is solely responsible for placing a DeepSeek web version entry at the bottom of the left sidebar in DeepSeek Harness (DSH), without handling any proxy, injection, or login logic. Maintained by Mystery-W, categorized under the client side, implemented in pure JavaScript, with no build steps and no third-party dependencies.

What is it¶

One sentence: A DeepSeek web shortcut entry plugin for the DSH left sidebar, to open / collapse chat.deepseek.com in the built-in browser on the right, or alternatively open it with the system browser.

• Name: mystery-w/dsh-deepseek-web-entry
• Maintainer: Mystery-W
• Components: Host half (a local fixed address route) + Client half (left sidebar entry)
• License: MIT
• Version: 1.0.1
• Requirements: Node.js >= 20

It solves the problem of “quickly reaching the web version of DeepSeek from Harness,” not “integrating the web version into an Agent.” This point will be elaborated on later.

Core Functions and Scope¶

The plugin adds a “DeepSeek Web Version” section at the bottom of the left sidebar, with the following behaviors:

The things it explicitly does not do define its boundaries:

• Does not proxy the web page: No local forwarding, no interface conversion, no wrapping the web page as an API;
• Does not inject scripts: Does not execute any code, does not read conversation content;
• Does not auto-login: Does not touch account names, passwords, CAPTCHAs, or save credentials;
• Does not consume API quota: It opens a web session, utilizing the web account;
• Unrelated to Marisa: Does not read/write to the Marisa project or files; can be installed and uninstalled independently.

In terms of implementation, the responsibilities of the files are clearly divided:

Installation and Enablement¶

The installation method provided in the README is installing via the Plugin Management page; it does not provide a single-line command like dsh plugin add, so do not try to concatenate it yourself.

Method 1: Install via Plugin Management Page (Recommended):

In the Harness “Plugins” page, select “Install Local / From URL”, fill in this repository’s address, or point directly to this directory.

Method 2: Install from local source code directory:

# Install this directory in Harness Plugin Management:
#   Plugins → Install → Local Directory → <this repository path>

Explanation of the plugin package structure (the dsh field in package.json):

"dsh": {
  "bundle": {
    "patch": "./cordis.patch.yml"
  },
  "client": {
    "platform": "web",
    "immediately": true,
    "inject": [
      "@deepseek-ai/dsh-client-ui-sidebar-right"
    ]
  }
}

The Client half declares a dependency on @deepseek-ai/dsh-client-ui-sidebar-right, which is Harness’s built-in right sidebar browser service. Therefore, the built-in browser part is not implemented by the plugin itself; it simply calls host capabilities.

After installation, you can run the offline self-check to verify if the sidebar slot and the two-click toggle logic are in place:

node selfcheck-client.mjs

Typical Usage¶

The plugin has no additional configuration files; it works immediately after installation. There are only two daily actions:

1. Want to quickly check the web version: Click the “DeepSeek Web Version” main button on the left sidebar; the built-in browser on the right expands and opens chat.deepseek.com; click again to collapse the right sidebar; the tab is retained for reuse next time.
2. Need a full web environment: Click the ↗ next to the main button to invoke the system default browser and open the same address. The README explicitly suggests using this path for daily use in the “Important Limitations” section; see below for reasons.

Applicable Scenarios and Notes¶

Suitable for: DSH users who want to minimize window switching and login actions for themselves or team members, and accept the premise that “the web version is just a web page in a browser.” The plugin only provides an entry point; it does not change the behavior of the web version itself.

Please note two points before installation.

First: The plugin runs with the permissions of the current DSH process. Its Host half registers a local route GET /deepseek-web/open-external, and its Client half injects UI into the left sidebar. Before installation, you should open index.js, client.js, and cordis.patch.yml to check the source code; the license is MIT.

Second: The README lists several known limitations; it is recommended to read them before use:

1. The embedded browser may be recognized as an “abnormal environment”: chat.deepseek.com may prompt “Use an abnormal environment, please use the official product” when inside an Electron webview, login may be restricted, and there is a risk of account risk control. Daily use is suggested to click ↗ to use the system browser.
2. The embedded browser cannot reuse Harness’s login state: Harness login is an API identity, while the web version uses a separate set of cookies; the first time requires a separate login in the embedded browser.
3. Cookies do not persist across application restarts (DSH official restriction): After restarting Harness, the embedded browser requires re-login; the system browser is not affected by this.
4. Not an official product: The plugin is unrelated to DeepSeek official services; using the web version requires compliance with DeepSeek’s Terms of Service.

In terms of security, the description provided in the README is quite restrained: the open-external route only accepts the hardcoded https://chat.deepseek.com/, does not accept parameters, and cannot be used to open arbitrary addresses; the plugin has no network requests, no file reading, and no tool registration. These descriptions come from the plugin’s own documentation, not an independent audit conclusion.

The directory page SkillHub classifies it under the client category and marks it with 0 stars. Note that SkillHub is an independent site with no official affiliation to DeepSeek or Hypersphere, and is not an official app store.

Conclusion¶

The value of dsh-deepseek-web-entry lies in its “lightness”: it only adds an entry point, without proxying, injecting, auto-login, or consuming API quota, and is clean to uninstall. If you are already accustomed to using the web version to handle conversations in DSH, this plugin can save you repetitive opening and login actions; if your team has requirements for auditing third-party materials, its small codebase, zero dependencies, and low source code audit cost are advantages.

• Directory: https://www.skillhub.cn/plugins/Mystery-W/dsh-deepseek-web-entry
• Repository: https://github.com/Mystery-W/dsh-deepseek-web-entry