JeffKeeping/dsh-purge-plus

Security & Privacy

A patcher for DeepSeek Harness that injects a custom red-team prompt kernel and ruleset into every session.

425
371
JavaScript
MIT
6 days old

If you already run DeepSeek Harness and want a fixed system prompt plus reusable rules injected on every turn without editing host prompt files, this fork targets you. It patches DSH 0.2, swaps in an encrypted default prompt, and adds a panel for toggling rule sets. Everyone else can stop here: it is a compatibility fork tied to one host version, not a general jailbreak toolkit.

The problem

A DSH user wants consistent prompt behavior across sessions and hosts without hand-editing prompt files each time or re-explaining rules at the start of every conversation. The stock workflow is manual: find the prompt file, edit it, remember to save, and repeat for Web and desktop separately. This plugin changes that step, backing up the matched host files on first Apply, replacing them, and injecting its own default prompt at turn start. The result is a session that begins with the author's red-team prompt and any activated rule set already in place.

What's different

Rather than a chat-side prompt you paste in, this is a host patcher. Apply writes backups as <file>.dshpurge.bak, replaces the matched files, overrides the shim, and injects an encrypted prompt shipped with the plugin. Per turn it decides from three inputs you control in the panel: the activated rule library (written to prompt-inject.md), checked local AGENTS.md/CLAUDE.md files in the current directory, and a workspace policy of strict, fallback or always. That gives repeatable rules across sessions instead of re-typing.

The cost is coupling. The README scopes support to dsh 0.2 only and warns against 0.1.x; older hosts must use the 1.1.39 or earlier line. Web and the official desktop EXE are separate hosts, and the README says to install and apply each separately because one does not reach the other. Patches that do not match stay pending or skipped, so after a host upgrade you may be applying less than you expect until the fork catches up. The fork also borrows approval-tier, audit-trail and revision-guard ideas from another project, which the README points to in NOTICE.md. Restore copies backups back and removes them, but that is a file-level revert, not a guarantee about every downstream effect.

Who should try it

Good fit: a DSH 0.2 user doing authorized red-team or prompt-research work who wants a fixed kernel and swappable rule sets across Web and desktop. Poor fit: anyone on 0.1.x, anyone wanting a general-purpose tool outside DSH, or anyone uncomfortable with a third-party plugin modifying host files. If dsh is not on PATH, the README documents a manual install that edits the profile directly; that path requires knowing which DSH home your host actually starts, and machines often have two.

Requirements and limitations

Version alignment is the main constraint: this fork targets 0.2.1-rc.2 and its neighbors, and mismatched patches are skipped rather than forced. Web and desktop are distinct hosts needing separate installs, so two environments mean two Apply steps and two sets of backups. Manual install asks you to edit only the profile for the host you run and warns not to touch the other or delete existing bundles. The README stresses it is a fork that does not change what the plugin does, only compatibility, kernel and UI, so upstream identity and licensing should be checked before relying on it. Ongoing care: after DSH updates, confirm /purge status reports the DSH home you actually run and that intended patches are not skipped. See the install and manual steps and the upstream release tags.

HotRepo's take

The repository was 6 days old at the 2026-10-25 observation and appeared on the NEW-REPOSITORY board for javascript at #17 with 425 total stars, which is a snapshot, not daily growth. HotRepo has no comparable daily-board history here, so persistence cannot be judged. Verify the target DSH version and host profile before applying.

Written by AI from the project's README, updated October 25, 2026. The project's own docs are the source of truth.