Yes, but only if the patch is reapplied using the complete README procedure; changing the preset alone does not update patches in the old process.

• The README specifically says that differences between standard and minimal/PTC modes may come from an uncleaned run_code or plan interception sentence in the preset, or from the built-in minimal preset lacking agent-instructions.
• For this case, it requires version 1.1.61 or newer, fully exiting the host, clicking “应用” in the Cleaning panel, allowing the automatic restart, and opening a new conversation round.
• The current project version is v1.1.71, which meets the minimum version stated in that section; the operator must still confirm that the official dsh 0.2 Web profile is running.
• The project provides stable/beta patch switching and status, apply, and revert operations, making it possible to verify whether the patch was actually loaded.

It can address the host patch paths covered by the project, but the README does not promise that every custom preset or PTC variant will be fixed.

Yes. It is suitable because the project explicitly targets controlled red-team evaluation on a local installation of official DeepSeek Harness and separates model behavior from Harness-level interception.

• The README states that Harness changes prompts, approval gates, sandbox behavior, and session format at runtime; the plugin can adjust default wording, permission policies, and tool limits.
• The official Web client uses the web profile, and the current version supports dsh 0.2. Web and desktop installations must be installed and applied separately.
• The “清洗” panel supports patch inspection, apply, revert, uninstall, prompt editing, and multiple rule sets. It also rechecks patches at startup after npm updates.
• The project is not a public-network scanner and contains no external attack payload, so it fits local, offline, or explicitly authorized environments rather than generalizing results to other platforms.

After installation, the host must be fully restarted, “应用” must be clicked, and a new conversation round must be opened; otherwise the injection will not enter the current session.

It depends. The plugin fits when the version and profile match, but multiple .dsh directories, the wrong installation path, or installing the Web package into the desktop profile can make the patch ineffective.

• The README explicitly supports official desktop EXE versions 0.2.0-rc.2 and 0.2.1-rc.2 through the desktop profile. Web packages cannot be used by the desktop client, and the two profiles must be installed and applied separately.
• Manual installation requires editing only the profiles/desktop/package.json belonging to the actually running host. Existing bundles must remain, and dsh-purge is appended to dsh.profile.bundles.
• Path discovery checks $DSH_HOME, the .dsh directory beside the launcher, user directories, and common Windows locations. The README warns that a machine may contain two .dsh directories.
• Node.js 18 or newer is required; Windows no-flash-window operation requires Node.js 22 or newer.

Thus it can support desktop debugging, but only after confirming the real DSH_HOME, profile name, and executable being launched.

It depends. The plugin provides a clear patch lifecycle, but it cannot guarantee complete recovery after every upgrade failure, abnormal termination, or path-selection mistake.

• The README says the plugin does not modify the Harness source repository directly; changes are applied from dsh-purge’s “清洗” panel, which provides apply, revert, uninstall, and status operations.
• Project insights state that original files are backed up before application. The plugin supports version matching, stable/beta switching, pinning older versions, and startup rechecking to address patches being overwritten by node_modules updates.
• Windows users must identify the actual $DSH_HOME. The README warns that two .dsh directories may exist, and changing the wrong one can make the plugin appear broken.
• Before uninstalling, the recovery boundary for the profile, node_modules, and configuration still matters; the project insight explicitly says backups do not guarantee complete recovery in every abnormal scenario.

It is therefore more suitable than manually editing packages for reversible experiments, but it should not be treated as an unconditional system-recovery tool.

It depends. The feature scope fits authorized evaluation, but it should not be adopted directly without reviewing and pinning the source.

• Project data lists v1.1.71 as the latest release, five releases in total, and an Other license. The README also says that future publishing channels and licensing terms may change; commercial use and derivative work require checking the current LICENSE.
• The README installation command uses the GitHub master.tar.gz archive and explicitly says that no dsh-purge package exists on npm. This makes installation convenient but does not pin a version.
• The project guidance recommends pinning and reviewing a specific release or commit before installation, and the project insight warns against using master without review.
• Archive installation targets official dsh web and the official desktop client; community desktop clients are not maintained, and the current version supports only dsh 0.2.

If the team can review the source, retain the archive and commit identity, and accept the Other license constraints, it can be used in an isolated evaluation environment. Otherwise, direct dependency adoption is not advisable.

Yes. It is suitable because the project treats prompts, rule sets, workspace rules, and host policies as separate controllable layers and supports switching configurations within one Harness installation.

• The README explicitly supports editing prompts and maintaining multiple rule sets; the project description says different models can use different prompts.
• The project insight states that injection decisions combine the rule library, workspace rule files, and plugin defaults, then process the workspace baseline using strict, fallback, or always policies.
• Workspace injection can be generated from AGENTS.md, CLAUDE.md, or a project rule library. The plugin also exposes commands such as rules list, rules use <id>, and rules create <id>.
• The README warns that changing only a preset or prompt does not update patches in the old process; the host must be fully exited, restarted, and opened with a new conversation.

Node.js 18 meets the minimum requirement, but the README provides neither cross-model results nor a standardized metric for prompt effectiveness.