Preface¶

DeepSeek Harness (DSH) is still in developer preview. If your daily usage extends beyond basic chat and running source code, and you desire capabilities such as a Windows desktop entry point, desktop alerts, community plugin management, MCP service management, model input type declaration, last message editing, sub-agent toggling, and official Team monitoring, dsh-enhanced-plugins is an enhancement suite that can be installed as a whole or selectively installed based on feature IDs.

It does not modify the DSH core; verified materials indicate that all Web functions are accessed via public plugin extension points. This article introduces its positioning, functions, installation commands, selection rules, and precautions based solely on verified facts.

What is this¶

The repository name for dsh-enhanced-plugins is sky-unicorn/dsh-enhanced-plugins, maintained by sky-unicorn. It consists of seven independently installable Cordis feature packages and a Windows companion, suitable for users who can already run the DSH Web profile from source.

Its value lies mainly in three aspects:

1. Adds a set of optional capabilities to DSH rather than replacing DSH itself.
2. Supports full installation, as well as selecting which Profile feature packages to retain based on stable feature IDs.
3. Provides Launcher, sound alerts, and desktop pet related capabilities specifically for the Windows desktop experience, while preserving the cross-platform usage of other functions.

Feature List¶

The verified functions are listed below. Feature IDs are used in the -Features parameter for installation commands.

windows-launcher is a required global component. It is added by the backend and does not need to be written in the -Features list, nor can it be removed via feature selection.

Pre-installation Checks¶

First confirm the environment and directory structure, then copy the installation command.

The requirements are as follows:

1. Node.js 22.19.x or Node.js 24 or higher.
2. A recent DSH Web profile that can run from source.
3. Verified compatible with DSH 0.1.2-alpha.2, local ABI baseline commit is 0a53fb55bea101816fa226bb964ae2bed71c343b.

Windows Launcher, native sounds, and desktop pet require a full Windows desktop edition and Windows PowerShell 5.1:

• Windows 10 version 1607 or higher;
• Windows 11.

Windows S mode, IoT / reduced-footprint editions, and Windows 10 1507, 1511 are not within this baseline. Other functions can be used as cross-platform features as described in the materials.

DSH is still in developer preview. If compatibility issues arise after upgrading DSH, first check the verified versions and commit, then determine if the issue is on the plugin side.

Install All Features¶

First check the directory relationship between DSH and dsh-enhanced-plugins.

If the two repositories share the same parent directory, for example:

<workspace>/
├── deepseek-harness/
└── dsh-enhanced-plugins/

Execute in the root directory of the dsh-enhanced-plugins repository:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\migrate-to-enhanced-plugin.ps1

Omitting -Features or passing -Features all will install the seven independent Cordis packages and the required Windows Launcher. This command only installs or updates program files; it does not start or open the Launcher.

If you wish to create a desktop shortcut at the same time, you can append -CreateLauncherDesktopShortcut:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\migrate-to-enhanced-plugin.ps1 `
  -CreateLauncherDesktopShortcut

If the DSH checkout is not a sibling directory, you need to explicitly pass the DSH source code path:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\migrate-to-enhanced-plugin.ps1 `
  -DshCheckout "E:\projects\deepseek-harness"

Before copying the command, confirm whether you belong to a sibling-directory install or a different-directory install. Do not omit -DshCheckout during a different-directory install.

Install Partial Features¶

If you only want partial capabilities, first list the stable feature IDs exposed by the current version:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\migrate-to-enhanced-plugin.ps1 -ListFeatures

Then pass the set of features you want to retain in the end. For example, only install desktop alerts, MCP management, and message editing:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\migrate-to-enhanced-plugin.ps1 `
  -Features notification,mcp-server-manager,edit-last-message

Here it is important to note: -Features is not an additive list. It describes the target project feature set that the Profile should ultimately retain.

For example:

• -Features none will remove the corresponding Profile packages for this project, but retain the Launcher;
• windows-launcher is a required global component and is not written in the -Features list;
• After selecting a feature, the installation process will still perform dependency installation, build, load verification, then clean up the aggregated package, unselected sibling features, declared legacy conflicts, and retired file-reference plugins.

Common Feature Combinations¶

The following combinations are common ones given in the materials and can directly replace the value of -Features.

Taking “Windows Desktop Experience” as an example:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\migrate-to-enhanced-plugin.ps1 `
  -Features windows-launcher,notification

Taking “Agent and Model Enhancements” as an example:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\migrate-to-enhanced-plugin.ps1 `
  -Features mcp-server-manager,model-input-types,edit-last-message,sub-agent

Taking “Plugin Discovery and Integration Management” as an example:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\scripts\migrate-to-enhanced-plugin.ps1 `
  -Features plugin-market,mcp-server-manager

Launcher Plugin Management¶

The control center of the Launcher provides a Plugin Management page. Verified materials indicate it supports:

1. Dynamic feature directory;
2. Maintaining desired state by Profile;
3. Single installation or removal;
4. Aggregated package migration;
5. Secure Git fetch / merge, or the use of exact-commit source ZIP fallback if Git is unavailable.

This means that after installation, you don’t necessarily have to go back to the command line to select features every time. If you want to adjust which capabilities a Profile retains later, you can enter the management entry from the Launcher, and then combine this with the “final feature set” semantics of -Features to understand the target state.

Scenarios and Precautions¶

dsh-enhanced-plugins is suitable for the following scenarios:

• You want to extend Web-side capabilities without modifying the DSH core.
• You mainly use DSH on Windows desktop and need Launcher, sound alerts, and desktop pets.
• You need to manage community plugins, MCP servers, model input types, last message editing, sub-agent toggling, and Team monitoring.
• You want to control which features a Profile ultimately retains based on feature IDs.

Precautions before use:

1. This plugin runs with the current dsh process permissions; you should check the source code and license before installation.
2. Verified materials do not provide the license text; you should rely on the repository’s current actual license before installation.
3. Plugin Community provides capabilities for searching, pre-checking, installing, and uninstalling community plugins; do not understand it as an official app store.
4. DSH is still in developer preview. If compatibility issues appear after upgrading DSH, first check the verified versions and commit.
5. -Features expresses the final retention set, not simply an additive list.

References¶

• Plugin Directory Page: https://www.skillhub.cn/plugins/sky-unicorn/dsh-enhanced-plugins
• GitHub Repository: https://github.com/sky-unicorn/dsh-enhanced-plugins