WebFV
Harness plugins / Field guide

dsh-purge: identify the plugin, version and local-lab limits

Read the current plugin documentation before relying on an old tutorial, choosing a host profile or removing an existing installation.

By WebFV Editorial · Checked October 24, 2026 · Plugin 1.1.77 · checked October 24, 2026

What the evidence coversOfficial README, package metadata and license files reviewed. No repository scripts, installation, host-policy changes, prompts or security tests were executed.

dsh-purge is a third-party plugin for an existing DeepSeek Harness installation. The source is YuJunZhiXue/dsh-purge. It is not DeepSeek Harness itself, and its README explicitly says it is not developed or endorsed by DeepSeek.

This page covers the public documentation at commit ac58b3e, checked October 24, 2026. We did not install the plugin, run its scripts, change a host policy, purchase model access or perform a security evaluation.

Identify the current package and host

The checked README and package.json both identify version 1.1.77. The package declares Node.js 18 or later and a target of DSH 0.2.1-rc.2. Those package declarations do not replace the host's own runtime requirements.

The README distinguishes the official Web profile (dsh web) from the official desktop EXE. Their installations and controls are separate. It also warns against applying the current line to a 0.1.x host; older host versions need the matching historical plugin release.

If you need the host rather than the plugin, start with our DeepSeek Harness setup guide. Installing Harness, adding a plugin to one profile and applying host modifications are different operations.

The current public build is local-lab only

The current README says that public-internet targets are closed. Its documented target restriction permits loopback and RFC1918 private addresses, resolves domain names before judging their addresses, and rejects public or mixed public answers and failed lookups. A private-looking domain suffix does not itself establish an allowed destination.

It also says this public build does not ship the skill library or knowledge base, and prohibits game-cheat uses. Older descriptions suggesting a bundled general-purpose attack library should not be presented as the current package contents.

These are upstream statements about the published build, not controls we tested. They do not establish permission to act on every system in a private network. This article provides no attack payloads, jailbreak prompts or target-operation recipes.

Where the documented installation route lives

Use the repository's current Install section after checking the installed host version and profile. It documents a GitHub tarball route through the Harness plugin command, plus a profile-specific pnpm alternative. It warns that the bare package name is not published on the npm registry and that the plugin-market route can remain queued.

For the official desktop host, the README also provides a dsh:// installation link. A browser opening that link does not demonstrate a completed installation. The documented profile package and bundle registration are the relevant installation records.

Review the package before installing: its metadata includes a postinstall script. Fetching a package can therefore involve code execution; it is not just reading this README. We inspected metadata only and did not run that script.

The plugin documentation separates registration from Apply, the operation that writes host changes. A registered plugin or visible dock is not proof that patches were applied successfully. This guide identifies the management entry points without walking through policy-removal or prompt-modification procedures.

Understand the management controls

The README describes a dsh-purge button beside the session title, opening a dock with Clean and Drill pages. Clean contains status and management controls; Drill is described as an authorization-gated local-lab interface.

For an existing installation, the documented status entry point is:

dsh-purge --status

This command is shown from documentation and was not executed here. Inspect the reported Harness home and host profile before interpreting status. A Web-profile observation should not be used as evidence about the desktop host.

Unmatched changes can be listed as pending or skipped. The README does not equate those states with successful application. Likewise, a host-side change does not guarantee that a model provider accepts a request or that every model behaves identically.

Restore and uninstall are not the same operation

The README describes Restore as returning backed-up host files while retaining the user's prompt-inject.md. It describes Uninstall as restoring applied changes first, then removing the injection file, rule library and plugin. Preserve any user-authored material you need before removal.

The documented UI route is dsh-purge → Clean → Uninstall, followed by its confirmation dialog. The README says this restarts the current host. Its terminal removal entry point is:

dsh-purge --uninstall

We did not run either route or verify restoration on a real installation. Removing a profile dependency alone should not be assumed to perform every restoration step described by the plugin's own uninstaller.

Read the license files together

The checked LICENSE, package metadata and NOTICE identify Apache License 2.0. The README separately says the original build may not be resold and requires attribution. LICENSE-COMMERCIAL.md asks commercial distributors to contact the author.

Those are the files' published statements. This guide does not resolve their legal interaction or describe the current version as MIT. Anyone planning redistribution should review the exact revision and clarify the terms with the maintainer rather than relying on a badge alone.

If an old tutorial disagrees

Compare its plugin version, host version, installation profile and publication date with the current source. A queued marketplace entry, the wrong Harness home or a mismatched host version calls for checking that specific condition, not repeatedly applying unrelated changes.

Claims such as “every model” in promotional text are not a compatibility test or a universal bypass guarantee. The supported conclusion here is narrower: the official repository documents a versioned third-party plugin with local management controls and a restricted public-build scope.