YuJunZhiXue/dsh-purge

Adoption takeaway: this is a niche, host-specific patching tool for people already running DeepSeek Harness and wanting to probe how its models respond to alternate system prompts. It is not a general LLM tool, and the README's own warnings place it in a legally sensitive zone.

The problem

A tester using DeepSeek Harness wants to compare how different models behave under a different persona or rule set, rather than the stock host prompt. The host ties prompts to its own packaged files, so changing that per session means editing files the host manages, and undoing it later is awkward. dsh-purge takes over that step: it patches the harness, injects a prompt shipped with the plugin, and lets the user switch prompt sets from a panel or chat commands. The result is a repeatable apply/revert cycle for prompt experiments inside one harness.

What's different

The mechanism is file patching plus in-process prompt injection, not an API integration. On Apply it backs up matched host files to .dshpurge.bak, replaces them, overrides a shim, and injects an encrypted default prompt so the prompt box shows a value without the user saving it. Prompts are organized as a rule library, with per-model swapping and workspace policy options. That gives fine control over which instruction set is active on each turn, and the revert path copies backups back. The trade-off is tight coupling: the plugin targets specific DSH versions, and mismatched patches stay pending or are skipped, so an upgrade can silently reduce its effect. The broader issue is purpose: the project calls itself a jailbreak harness, which puts its use in tension with provider terms and, depending on jurisdiction, legal boundaries; the README carries a long compliance disclaimer that shifts responsibility to the user.

Who should try it

A good fit is someone doing authorized red-team or robustness evaluation of DeepSeek Harness deployments, who can reproduce results on a disposable install and understands the host's profile layout. A poor fit is anyone wanting a portable prompt-testing workflow across providers, or a shared team environment: the patching design and version pinning make that awkward, and the compliance disclaimers make unsupervised use hard to justify. Users on older DSH 0.1.7 need an older release tag, which changes setup substantially.

Requirements and limitations

Version 1.1.79 targets DSH 0.2.1-rc.2, with 0.2.0 still working; 0.1.x needs 1.1.39 or older. The plugin marketplace path fails per the README, so installation is a manual profile edit or direct command, and machines with multiple DSH homes require identifying the right one. Ongoing upkeep means matching plugin and host versions on each update. The software is Apache-2.0, but redistribution must keep the NOTICE and attribution, and resale is prohibited. The README also warns that using it for crime is solely the user's liability, which is a real constraint on organizational adoption, not boilerplate.

HotRepo's take

HotRepo recorded 7,558 stars on 2026-10-19, then 11,039 on 2026-10-20 and 10,634 on 2026-10-27, three daily-board observations in all. With that sparse sample, persistence cannot be judged. Before installing, verify the exact DSH version you run against the supported-host table in the project README and its releases.