dsh-purge: A Red-Team Dock on DeepSeek Harness That Separates Refusal from Host Blocks

What Does It Do?

It is a cybersecurity red-team DSH plugin for DeepSeek Harness that separates a host-layer block from a model refusal on your own installation. The harness does more than forward a prompt: it rewrites prompts, approval gates, sandbox policy, and session migration at runtime, so asking only "will the model answer" can mistake a host policy for a refusal. This plugin lets you run controlled evaluation and see which default policy is too tight, and it supports both official Web and the official desktop build, which must be installed and applied separately.

Core Features

• dsh-purge dock: a button beside the session title opens a right-hand dock with two pages, Clean and Drill.
• Clean page: grouped patch status plus Apply / Restore / Uninstall, a prompt editor, and multiple rule sets.
• Drill page: built into the stable release; after authorization it covers assets, skills, and the local environment, only for a host you manage, an offline target, or a written authorized exercise.
• Host policy handling: default copy, permission policy, and tool limits, while official capabilities stay and no second invented identity is added.
• On start it checks and reapplies, so after npm overwrites node_modules you do not hand-edit files.
• Path detection without hardcoded drive letters: it looks at $DSH_HOME, .dsh next to the dsh launcher, then ~/.dsh, and it does not patch the Harness source tree.

How to Use This Plugin?

Adding the plugin to a profile does not patch the host; you click dsh-purge beside the session title, then Clean, then Apply, and that Apply is what writes the changes. A successful Apply restarts, an unfinished Apply does not, and after the restart you start a new chat, which is when the inject enters the session. Official Web uses the web profile and the official desktop EXE uses the desktop profile, so install and apply them separately; this release targets dsh 0.2, and older dsh builds need the matching older plugin. Identity comes from the encrypted prompt shipped in the plugin, the text the prompt box shows by default, and the host prompt file is not read. Node.js 18 or newer is required, and Windows no-flash needs Node 22 or newer.

How to Troubleshoot This Plugin?

Nothing changes after Apply: confirm you finished Apply on the Clean page, since an unfinished Apply does not restart, and remember a new chat is needed after the restart for the inject to take effect. Only one of Web or desktop works: check that each was installed and applied under its own profile, as they do not share one patch. Version mismatch: this release targets dsh 0.2, so older dsh builds need the matching older plugin. It stops working after npm overwrites node_modules: the plugin checks and reapplies on start, so no manual file editing is needed.