Skip to content
Back to search

dsh-purge1.7.3-

DeepSeek Harness 破甲:让所有模型都能破甲,不同模型可换不同提示词;默认提示词面向国模「小码酱」。Jailbreak for every model — swap prompts per model. 求 Star 收藏 ⭐ 如要二开,请查看署名要求部分

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked yesterday
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/yu994419160--dsh-purge1-7-3/badge.svg)](/listings/yu994419160--dsh-purge1-7-3)

HTML

<a href="/listings/yu994419160--dsh-purge1-7-3"><img src="/api/listings/yu994419160--dsh-purge1-7-3/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Web and the official desktop EXE are the two maintained hosts. Install and patch each **separately**, and only the host you actually run.

| What you run | Profile | Command | |---|---|---| | Official `dsh web` | `web` | `dsh plugin --profile web add https://github.com/YuJunZhiXue/dsh-purge/archive/refs/heads/master.tar.gz` | | Official desktop EXE | `desktop` | `dsh plugin --profile desktop add https://github.com/YuJunZhiXue/dsh-purge/archive/refs/heads/master.tar.gz` |

If this directory is already a clone, use `add .` instead of the URL. If `dsh` is not on PATH, use [Manual install](#manual). There is no npm package; do not `pnpm add dsh-purge`.

For the desktop client you can also click the button (`dsh://` deep link):

<p align="center"> <a href="dsh://plugin/install?id=dsh-purge&name=dsh-purge&version=1.1.73&repo=YuJunZhiXue%2Fdsh-purge&permissions=%E7%B3%BB%E7%BB%9F%E6%8F%90%E7%A4%BA%E8%AF%8D%E6%B3%A8%E5%85%A5%2C%E6%9C%AC%E6%9C%BA%E8%A1%A5%E4%B8%81%2C%E8%AE%BE%E7%BD%AE%E9%A1%B5&downloadUrl=https%3A%2F%2Fgithub.com%2FYuJunZhiXue%2Fdsh-purge%2Farchive%2Frefs%2Fheads%2Fmaster.tar.gz"><strong>Install in desktop client</strong></a> </p>

After the command: three steps

Adding the plugin to a profile does **not** patch `@deepseek-ai` by itself.

1. **Quit and reopen** the host you installed into — stop and restart `dsh web`, or quit the desktop tray and reopen that app. 2. On **that host**, click **dsh-purge** beside the session title, then **Apply** on the **Clean** page. It is not on the host Settings page. 3. A successful **Apply** restarts once so patches load. It does not restart if it did not finish.

Web controls affect Web only; desktop controls affect the desktop app only. Do not Apply one host from the other.

How to tell it installed

- **dsh-purge** sits beside the session title, with **Apply** on its Clean page. - `/purge status` in chat prints `DSH_HOME` and the patch list — the path should be the home you actually run. - Optional packages that are not installed (liangshen) show as skipped and do not block Apply.

Hand this to an assistant

Paste the block below to a local assistant. It should only run the install command — no disk scan, no other edits, no Apply, no restart.

<details> <summary><strong>For AI assistants (install only)</strong></summary>

Install the DeepSeek Harness plugin `dsh-purge` into the Web profile only. Do not scan the whole disk, do not read or edit other files, do not apply settings, and do not restart the app. Do not install into the desktop profile.

**Web (official `dsh web`)**

If `dsh` is not on PATH, tell the user and stop.

dsh plugin --profile web add https://github.com/YuJunZhiXue/dsh-purge/archive/refs/heads/master.tar.gz

If this directory is already a clone, use `dsh plugin --profile web add .`. There is no npm package; do not `pnpm add dsh-purge`.

After the command finishes, tell the user to fully quit and restart `dsh web`, then open **dsh-purge** beside the session title and **Apply** on **Clean**. Then stop.

</details>

<a id="manual"></a>

Manual install

Use this when the command fails or `dsh` is not on PATH. Edit **only the profile for the host you run** — do not touch the other, and do not delete existing bundles.

<details> <summary><strong>Full manual steps</strong></summary>

**1. Find the `$DSH_HOME` this host uses.** A real home is named `.dsh` (official EXE sometimes `dsh-home`), contains `profiles`, and has at least one `profiles/<name>/package.json`. Check in order: `DSH_HOME` env → `.dsh` next to the install root (portable) → `%USERPROFILE%\.dsh` or `~/.dsh` → `%APPDATA%` / `%LOCALAPPDATA%\DeepSeek Harness\dsh-home`. Confirm: `profiles/web/package.json` has `"name": "dsh-profile-web"` (or `dsh-profile-desktop`). Machines often have two homes — use the one that belongs to the host you actually start.

PowerShell to list candidates:

$cands = @()
if ($env:DSH_HOME) { $cands += $env:DSH_HOME }

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 557 lines
  1. <p align="center">
  2. <img src="docs/banner.svg" alt="dsh-purge" width="720">
  3. </p>
  4. <h1 align="center">⚔️ DeepSeek Harness cybersecurity red-team tool (dsh-purge)</h1>
  5. <p align="center"><strong>Version 1.1.73</strong></p>
  6. <p align="center">
  7. <em>DeepSeek Harness jailbreak: every model, swap prompts per model. Default prompt for 小码酱. Please star ⭐ If you build on this, see Attribution required.</em>
  8. </p>
  9. <p align="center">
  10. <a href="https://github.com/YuJunZhiXue/dsh-purge/stargazers"><img src="https://img.shields.io/github/stars/YuJunZhiXue/dsh-purge?logo=github&label=Stars" alt="GitHub stars"></a>
  11. <a href="https://github.com/YuJunZhiXue/dsh-purge/blob/master/LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-blue?style=flat" alt="Apache-2.0"></a>
  12. <a href="https://awesome-dsh-plugin.com"><img src="https://awesome-dsh-plugin.com/badge.svg" alt="awesome · DSH plugin"></a>
  13. <a href="https://deepseek.stream/plugins/dsh-purge"><img src="https://img.shields.io/badge/Hub-dsh--purge-1a73e8" alt="DeepSeek Harness Hub"></a>
  14. <a href="https://www.deepseek.com/harness/"><img src="https://img.shields.io/badge/dsh-0.2.0--rc.2%20%2F%200.2.1--rc.2-blue" alt="DSH"></a>
  15. <br>
  16. <img src="https://img.shields.io/badge/Node.js-%3E%3D18-339933?logo=node.js&logoColor=fff" alt="Node.js">
  17. <img src="https://img.shields.io/badge/JavaScript-F7DF1E?logo=javascript&logoColor=000" alt="JavaScript">
  18. </p>
  19. <p align="center">
  20. <a href="https://dsh-plugin.org/plugins/yujunzhixue/dsh-purge"><img src="https://dsh-plugin.org/badges/listed.svg" alt="Listed on dsh-plugin.org"></a>
  21. </p>
  22. <p align="center">
  23. <a href="README.md">English</a> | <a href="README.zh-CN.md">中文</a>
  24. </p>
  25. ## A note from the author
  26. People have been selling this open-source work in the open. After that, the author was asked to come in and talk. No need to spell out the rest. Read between the lines.
  27. From now on the **public internet is closed**. Attack tasks only allow lab targets: localhost / private nets, known ranges, and the one host you registered. A public IP or some random domain does not pass.
  28. **The original build may not be resold.** Charging for it, skinning it, or hawking it in groups is not allowed. Forks are fine, but **you must attribute** and name the source: [YuJunZhiXue/dsh-purge](https://github.com/YuJunZhiXue/dsh-purge). Hide the source or pass it off as your own, and you are on the other side.
  29. The author's personal channel: [t.me/LLM_PoJia](https://t.me/LLM_PoJia). Notes and updates show up there.
  30. ## Contents
  31. - [A note from the author](#a-note-from-the-author)
  32. - [What this is](#what-this-is)
  33. - [Attribution required](#attribution-required)
  34. - [License](#license)
  35. - [Supported hosts](#supported-hosts)
  36. - [Install](#install)
  37. - [Preview](#preview)
  38. - [Usage](#usage)
  39. - [Own servers](#own-servers)
  40. - [How it works](#how-it-works)
  41. - [Restore](#restore)
  42. - [Releases](#releases)
  43. ---
  44. ## What this is
  45. **dsh-purge** is a cybersecurity red-team plugin for the official [DeepSeek Harness](https://www.deepseek.com/harness/) already installed on your machine. **1.1.73** targets **DSH 0.2.1-rc.2** (0.2.0 still works). Official **Web** (`dsh web`) and the official **desktop EXE** are both supported. Install and Apply them separately.
  46. Harness does more than forward a prompt. It rewrites prompts, approval gates, sandbox policy, and session migration at runtime. Asking only “will the model answer” treats a host-layer block as a model refusal. This plugin separates those two layers on your own install, for controlled evaluation and for seeing which default policy is too tight.
  47. | You get | What it does |
  48. |---|---|
  49. | **dsh-purge dock** | A button beside the session title opens the right dock. Two pages: Clean and Drill |
  50. | **Clean** | Grouped patch status, Apply / Restore / Uninstall, prompt editor, multiple rule sets |
  51. | **Drill** | Built into the stable release. After authorization: assets, skills, and the local environment. Only for a host you manage, an offline target, or a written authorized exercise |
  52. | **Host policy** | Default copy, permission policy, and tool limits. Official capabilities stay. No second invented identity |
  53. | **On start** | Checks and reapplies. After npm overwrites `node_modules`, you do not hand-edit files |
  54. No hardcoded drive letters. It looks at `$DSH_HOME`, `.dsh` next to the dsh launcher, then `~/.dsh`. It does not patch the Harness source tree. **Apply** on the **Clean** page of **dsh-purge** is what writes the changes. Identity comes from the encrypted prompt shipped in the plugin, the text the prompt box shows by default. The host prompt file is not read.
  55. It only touches the official `@deepseek-ai` packages and local config on the user's machine. It is not a public scanner and not an attack kit for third-party sites. The repo does not ship malware, unauthorized-exploit scripts, or payloads aimed at the public internet.
  56. ---
  57. ## The original may not be resold. Forks must attribute.
  58. ## Attribution required
  59. **The original build may not be resold.** No paid resale, no skinned store listing, no hawking it in groups.
  60. **Forks must attribute** and name the source repository: [YuJunZhiXue/dsh-purge](https://github.com/YuJunZhiXue/dsh-purge). Same if you borrow the name, ideas, code, or prompts.
  61. Hiding the source, passing it off as your own, or reselling the original will be pursued.
  62. ## License
  63. This repo is [Apache License 2.0](./LICENSE). Forks and redistributions must keep the copyright notice and [NOTICE](./NOTICE), and name [YuJunZhiXue/dsh-purge](https://github.com/YuJunZhiXue/dsh-purge). The original may not be resold.
  64. ---
  65. <a id="strict-legal--compliance-disclaimer"></a>
  66. <div>
  67. ### ⚠️ <font color="red">Strict legal and compliance disclaimer</font>
  68. <font color="red">
  69. **Disclaimer:** This is a non-profit open-source project. It follows applicable laws and the rules of the platforms it uses, and is intended only for learning and research. Do not use it for any illegal or non-compliant purpose; the user bears any resulting consequences.
  70. **Zero-tolerance statement:** This project opposes and forbids any illegal activity. The authors do not support, encourage, or assist unauthorized network attacks, exploit use, data theft, unlawful intrusion into computer information systems, or generation of illegal or prohibited content. **Anyone who uses this project for crime is solely responsible under the law. The authors have no liability.**
  71. 1. **This repository contains no illegal material.** The published code, docs, patches, and default prompt are **not** malware, backdoors, unauthorized pentest kits, ransomware, credential-stuffing scripts, or attack payloads aimed at the public internet or third-party systems. The project does not supply illegal content and does not incite, organize, or assist crime.
  72. 2. **Local official Harness only.** Security-eval patches and prompt injection run only on the **official DeepSeek Harness already installed on the user's machine** (`@deepseek-ai` packages, local profile / `$DSH_HOME`). The target is the user's own official local software, **not** someone else's website, server, account, or information system.
  73. 3. **Eval patches do not attack the public internet.** Apply, inject, revert, and uninstall stay in local files and local processes. They **do not scan, probe, intrude, or send attack traffic to any public host or unauthorized system**. Do not use this project as a jump host against the public internet. If "check for updates" is on, the plugin may only contact this plugin's own GitHub repository to compare versions. That is **not** an attack on third-party systems and is **not** authorization to penetrate anything.
  74. 4. **Lawful, controlled scope.** This project is an aid for red-team research and robustness evaluation on an **official Harness the user is entitled to administer**. **Do not run it against targets without the owner's lawful written authorization, public online systems, or production workloads.** Testing must stay on the **authorized local official Harness, offline local synthetic fixtures, authorized cybersecurity ranges, and compliant lab environments**.
  75. 5. **Anything that is not a lab target is forbidden.** Attack tasks only allow localhost/private nets, known range platforms, and one exact IP or exact hostname that the user registered in advance as their own server. A public IP, any other domain, or a cloud-provider name is not an exception. A key, a password, a network range, a wildcard, or a claim made in the conversation does not add an exception. Anything that is not registered stays forbidden.
  76. 6. **Forbidden uses.** Users must not use this project, directly or indirectly, to violate the following (each must be followed; no excuse to evade):
  77. - <font color="red"><strong>Criminal Law of the People's Republic of China</strong></font>
  78. - <font color="red"><strong>Cybersecurity Law of the People's Republic of China</strong></font>
  79. - <font color="red"><strong>Data Security Law of the People's Republic of China</strong></font>
  80. - <font color="red"><strong>Personal Information Protection Law of the People's Republic of China</strong></font>
  81. - and other applicable laws, regulations, and supervisory rules;
  82. - Also forbidden:
  83. - Unauthorized intrusion or attacks on public or private computer information systems; extortion, sabotage, credential stuffing, or spreading malicious payloads;
  84. - Inducing, generating, or spreading any content the law forbids, including threats to national security, terrorism, violence, pornography, gambling, fraud, and privacy or intellectual-property infringement;
  85. - Violating the model provider's terms of service and acceptable-use policy.
  86. 7. **The user bears all responsibility.** The project is provided under Apache-2.0 as-is. The authors make no warranty of completeness, security, or fitness. **Users independently bear all civil, administrative, and criminal liability** for download, deploy, run, modify, distribute, and all resulting inputs and outputs. Authors and contributors bear no direct, indirect, or joint liability for abuse.
  87. 8. **The license ends on breach.** Anyone who uses this project for illegal attacks, malicious activity, or other violations has their open-source license **automatically and irrevocably terminated** from the moment of the violation. They must stop using the project, permanently destroy all copies and derivatives, and accept legal sanctions.
  88. 9. **No affiliation.** This is an independent open-source security-eval research project. It has no employment, commercial, authorization, or endorsement relationship with DeepSeek or its affiliates. "Official" here only means the eval target is the official DeepSeek Harness package on the user's machine. It does **not** mean DeepSeek developed, approved, or warrants this plugin.
  89. 10. **Attribution is required.** If you borrow this project's name, ideas, code, or prompts, you must credit the author and name this repository. Failure to attribute will be pursued. See [Attribution required](#attribution-required).
  90. </font>
  91. </div>
  92. ---
  93. ## Supported hosts
  94. **1.1.73 targets DSH 0.2.1-rc.2.** 0.2.0 still works. Do not apply it to 0.1.x.
  95. - **dsh 0.2.1-rc.2** (official desktop / official `dsh web`): use **1.1.73**. Fixes `{{cwd}}` / `[cwd]` crash, patch #40 match, dropped `toolFilter`, host `dsh-tools` resolve, hostFs fd, desktop helper self-kill, `file:` archive update, Ctrl+Enter steer.
  96. - **dsh 0.2.0-rc.2**: use **1.1.40** or newer; this line also installs.
  97. - **dsh 0.1.7** (incl. rc.1 / rc.2): use **1.1.39** or older — pick the tag on [Releases](https://github.com/YuJunZhiXue/dsh-purge/releases).
  98. Unmatched patches stay pending or skipped; nothing is rewritten blindly.
  99. ---
  100. ## Install
  101. Web and the official desktop EXE are the two maintained hosts. Install and patch each **separately**, and only the host you actually run.
  102. | What you run | Profile | Command |
  103. |---|---|---|
  104. | Official `dsh web` | `web` | `dsh plugin --profile web add https://github.com/YuJunZhiXue/dsh-purge/archive/refs/heads/master.tar.gz` |
  105. | Official desktop EXE | `desktop` | `dsh plugin --profile desktop add https://github.com/YuJunZhiXue/dsh-purge/archive/refs/heads/master.tar.gz` |
  106. If this directory is already a clone, use `add .` instead of the URL. If `dsh` is not on PATH, use [Manual install](#manual). There is no npm package; do not `pnpm add dsh-purge`.
  107. For the desktop client you can also click the button (`dsh://` deep link):
  108. <p align="center">
  109. <a href="dsh://plugin/install?id=dsh-purge&name=dsh-purge&version=1.1.73&repo=YuJunZhiXue%2Fdsh-purge&permissions=%E7%B3%BB%E7%BB%9F%E6%8F%90%E7%A4%BA%E8%AF%8D%E6%B3%A8%E5%85%A5%2C%E6%9C%AC%E6%9C%BA%E8%A1%A5%E4%B8%81%2C%E8%AE%BE%E7%BD%AE%E9%A1%B5&downloadUrl=https%3A%2F%2Fgithub.com%2FYuJunZhiXue%2Fdsh-purge%2Farchive%2Frefs%2Fheads%2Fmaster.tar.gz"><strong>Install in desktop client</strong></a>
  110. </p>
  111. ### After the command: three steps
  112. Adding the plugin to a profile does **not** patch `@deepseek-ai` by itself.
  113. 1. **Quit and reopen** the host you installed into — stop and restart `dsh web`, or quit the desktop tray and reopen that app.
  114. 2. On **that host**, click **dsh-purge** beside the session title, then **Apply** on the **Clean** page. It is not on the host Settings page.
  115. 3. A successful **Apply** restarts once so patches load. It does not restart if it did not finish.
  116. Web controls affect Web only; desktop controls affect the desktop app only. Do not Apply one host from the other.
  117. ### How to tell it installed
  118. - **dsh-purge** sits beside the session title, with **Apply** on its Clean page.
  119. - `/purge status` in chat prints `DSH_HOME` and the patch list — the path should be the home you actually run.
  120. - Optional packages that are not installed (liangshen) show as skipped and do not block Apply.
  121. ### Hand this to an assistant
  122. Paste the block below to a local assistant. It should only run the install command — no disk scan, no other edits, no Apply, no restart.
  123. <details>
  124. <summary><strong>For AI assistants (install only)</strong></summary>
  125. <!-- AI-AGENT-START -->
  126. Install the DeepSeek Harness plugin `dsh-purge` into the Web profile only. Do not scan the whole disk, do not read or edit other files, do not apply settings, and do not restart the app. Do not install into the desktop profile.
  127. **Web (official `dsh web`)**
  128. If `dsh` is not on PATH, tell the user and stop.
  129. ```sh
  130. dsh plugin --profile web add https://github.com/YuJunZhiXue/dsh-purge/archive/refs/heads/master.tar.gz
  131. ```
  132. If this directory is already a clone, use `dsh plugin --profile web add .`. There is no npm package; do not `pnpm add dsh-purge`.
  133. After the command finishes, tell the user to fully quit and restart `dsh web`, then open **dsh-purge** beside the session title and **Apply** on **Clean**. Then stop.
  134. <!-- AI-AGENT-END -->
  135. </details>
  136. <a id="manual"></a>
  137. ### Manual install
  138. Use this when the command fails or `dsh` is not on PATH. Edit **only the profile for the host you run** — do not touch the other, and do not delete existing bundles.
  139. <details>
  140. <summary><strong>Full manual steps</strong></summary>
  141. **1. Find the `$DSH_HOME` this host uses.** A real home is named `.dsh` (official EXE sometimes `dsh-home`), contains `profiles`, and has at least one `profiles/<name>/package.json`. Check in order: `DSH_HOME` env → `.dsh` next to the install root (portable) → `%USERPROFILE%\.dsh` or `~/.dsh` → `%APPDATA%` / `%LOCALAPPDATA%\DeepSeek Harness\dsh-home`. Confirm: `profiles/web/package.json` has `"name": "dsh-profile-web"` (or `dsh-profile-desktop`). Machines often have two homes — use the one that belongs to the host you actually start.
  142. PowerShell to list candidates:
  143. ```powershell
  144. $cands = @()
  145. if ($env:DSH_HOME) { $cands += $env:DSH_HOME }
  146. $cands += "$env:USERPROFILE\.dsh"
  147. $dsh = Get-Command dsh -ErrorAction SilentlyContinue
  148. if ($dsh) {
  149. $dir = Split-Path $dsh.Source
  150. $cands += @((Join-Path $dir ".dsh"), (Join-Path (Split-Path $dir) ".dsh"), (Join-Path (Split-Path (Split-Path $dir)) ".dsh"))
  151. }
  152. $cands += @("$env:APPDATA\DeepSeek Harness\dsh-home", "$env:LOCALAPPDATA\DeepSeek Harness\dsh-home")
  153. $cands | Select-Object -Unique | Where-Object { $_ -and (Test-Path (Join-Path $_ "profiles")) }
  154. ```
  155. **2. Put the plugin at `$DSH_HOME/plugins/dsh-purge`** (folder must be named `dsh-purge`, with a `package.json` whose `"name"` is `dsh-purge`).
  156. ```sh
  157. git clone https://github.com/YuJunZhiXue/dsh-purge.git "$DSH_HOME/plugins/dsh-purge"
  158. ```
  159. Without git: download [master.tar.gz](https://github.com/YuJunZhiXue/dsh-purge/archive/refs/heads/master.tar.gz), extract, rename `dsh-purge-master` → `dsh-purge`, and place it under `plugins`. If you already have a clone, copy the whole tree — not a few `.js` files.
  160. **3. Edit only that profile's `package.json` — back it up first.** Web → `$DSH_HOME/profiles/web/package.json`; desktop → `$DSH_HOME/profiles/desktop/package.json`. Add **only two things**, keeping every existing dependency and bundle:
  161. 1. In `dependencies`, add `"dsh-purge": "file:../../plugins/dsh-purge"`
  162. 2. At the **end** of `dsh.profile.bundles`, append `"dsh-purge"` (skip if already there)
  163. ```json
  164. {
  165. "name": "dsh-profile-web",
  166. "private": true,
  167. "dependencies": {
  168. "dsh-purge": "file:../../plugins/dsh-purge"
  169. },
  170. "dsh": {
  171. "profile": {
  172. "bundles": [
  173. "@deepseek-ai/dsh-base",
  174. "@deepseek-ai/dsh-web-app",
  175. "dsh-purge"
  176. ],
  177. "patchReload": "live"
  178. }
  179. }
  180. }
  181. ```
  182. Keep JSON valid (comma before the new item, none after the last). Do not switch `file:../../plugins/dsh-purge` to an absolute path, do not touch `patchReload` or other plugins, and do not list `"dsh-purge"` twice. On desktop, if there is no `dsh-web-app` row, do not add one.
  183. **4. Run `pnpm install` in that profile only** (`cd` into the profile dir, not the repo root or `$DSH_HOME`):
  184. ```sh
  185. cd "$DSH_HOME/profiles/web" # or profiles/desktop
  186. pnpm install
  187. ```
  188. Success: `profiles/<web|desktop>/node_modules/dsh-purge/package.json` exists. If `pnpm` is missing, use the Node / pnpm shipped with official `dsh`; on `Could not resolve`, re-check the `file:` path; on a JSON error, fix commas or restore the backup.
  189. **5. Fully quit that host, reopen it, then Apply** — same three steps as above. The card appears beside the session title; click **Apply** (or `/purge apply`) on that host only. If the card is missing, you likely edited the other `.dsh` — go back to step 1.
  190. </details>
  191. ### Uninstall
  192. **dsh-purge** beside the session title → **Clean** → **Uninstall**. Confirm the dialog: it reverts any applied patches, restores the original Harness, and restarts the current host.
  193. ```sh
  194. # or from a terminal / chat
  195. dsh-purge --uninstall
  196. # /purge uninstall
  197. ```
  198. Plugin config lives in `cordis.patch.yml` (`postPrompt` is empty by default):
  199. ```yaml
  200. - insert:
  201. - id: dsh-purge
  202. name: 'dsh-purge'
  203. config:
  204. enabled: true
  205. autoApplyOnStart: true
  206. autoUpdateOnStart: false
  207. autoRevertOnMissing: false
  208. verbose: false
  209. postPromptOrder: 5100
  210. postPrompt: ""
  211. ```
  212. ---
  213. ## Preview
  214. **dsh-purge** sits beside the session title. It opens a right-hand dock with two pages: **Clean** and **Drill**. Switch **Light / Ink**. Patches are grouped; the count only includes items that actually applied. Rule sets sit in a list above the editor, with Enable and Delete on each row.
  215. The first time you open Drill you read the notice, wait out the countdown, scroll to the end, and check three boxes. Clean does not need that step. Drill is only for a host you manage, an offline target, or an exercise that already has written authorization.
  216. **Clean**
  217. ![Clean](docs/preview/dock-clean.png)
  218. **Drill authorization**
  219. ![Drill authorization](docs/preview/dock-auth.png)
  220. **Drill**
  221. ![Drill](docs/preview/dock-drill.png)
  222. **Patches**
  223. ![Patches](docs/preview/settings.png)
  224. **Own servers**
  225. On the Clean page, under Prompt. One host per line, then Save list. Steps are in [Own servers](#own-servers).
  226. ![Own servers](docs/preview/own-servers-en.png)
  227. | Area | What it shows |
  228. |---|---|
  229. | dsh-purge | button beside the session title; opens or collapses the dock |
  230. | Clean | the old Rules page: patches, prompt, rule sets, skills |
  231. | Drill | assets, skills, and environment after authorization. The tab says Unauthorized until then |
  232. | Patches | grouped status, Apply, Restore, or Uninstall |
  233. | Prompt | edit `prompt-inject.md` as the session override |
  234. | Own servers | one IP or exact hostname per line, saved to `$DSH_HOME/net-scope-allow.txt` |
  235. | Rule sets | multiple `AGENTS.md` / `CLAUDE.md`; Enable writes under `$DSH_HOME`, Delete removes the row |
  236. | Skills | import a zip or folder into this host’s official `$DSH_HOME/skills/<id>/SKILL.md` (web and desktop each use their own home; no drive letter is hardcoded); DSH owns match, load, and `/name`. You can also delete that folder yourself |
  237. ---
  238. ## Layout
  239. `bin/` is the CLI, `lib/` is patches and the drill console, `presets/redteam/` is the red-team preset, `skills/redteam/` is bundled red-team skills, `skills/paper-autopilot/` is the bundled paper skill, and `client.js` is the dock.
  240. ### Bundled skill: paper-autopilot
  241. `skills/paper-autopilot/` is a 22-step thesis pipeline (Chinese dissertation / SCI). It is not a jailbreak patch and is not auto-injected.
  242. ```sh
  243. node scripts/install-paper-autopilot.mjs
  244. node scripts/install-paper-autopilot.mjs --dry-run
  245. node scripts/install-paper-autopilot.mjs --json
  246. ```
  247. Install is copy-only. An existing folder is renamed `paper-autopilot.bak-<timestamp>`. Trigger with “write a paper / thesis” or `/paper`.
  248. Runtime files live under `$DSH_HOME`: `prompt-inject.md`, `rules/`, `skills/`, `net-scope-allow.txt`, `redteam/`. If `DSH_HOME` is unset, the launcher-adjacent `.dsh` wins over `~/.dsh`. Web and the desktop app each use their own home. Skills are not part of the inject section and do not replace the prompt.
  249. ---
  250. ## Usage
  251. ```sh
  252. dsh-purge --status
  253. dsh-purge --apply
  254. dsh-purge --revert
  255. dsh-purge --uninstall
  256. dsh-purge --edit
  257. /purge status | apply | revert | uninstall | edit | help
  258. /rules list | use <id> | create <id> | delete <id> | reset | help
  259. /skills list | import <zip-or-folder> | create <id> [description] | delete <id> | help
  260. /rewind
  261. purge_status purge_apply purge_revert
  262. ```
  263. After a successful Apply, the host restarts so patched packages load; you can also click **Restart** manually. Under the patch title are the stable release and the test release. The test release follows the `beta` branch. **Switch to stable** installs `master` and clears any pin. Picking an older stable version pins it; click **Update** to return to the latest. Old test tags are not listed.
  264. The composer **Undo once** and **Undo last round** stay in the current conversation and do not open a branch. The sent line goes back into the input, and that cut's already-sent messages and completed tasks leave the current conversation; edit and **send again**. From **1.1.61**, rewind bounds follow the **current turn**, not the first user message. `/rewind` does the same.
  265. If the **same task works in standard but fails in minimal or PTC**, preset `run_code`, sandbox, or plan intercept text is often still uncleared, or built-in minimal is missing `agent-instructions`. Use **1.1.61+**, then **quit the host fully → Apply in Clean → restart → start a new chat**. Switching preset alone does not reload patches in the running process.
  266. ### Response speed
  267. DSH runs Bash calls in a tool batch one at a time. Older dsh-purge releases raised the default foreground wait from 60 seconds to 10 minutes, so one slow command could hold up later calls for that long. Patch #21 now restores marked plugin values to the official 60-second default. Unmarked timeouts and other custom values are preserved; an unmarked 10-minute value cannot reliably be distinguished from a user setting.
  268. For a shorter wait in `dsh web` on macOS/Linux, add this entry to `$DSH_HOME/profiles/web/cordis.patch.yml` (normally `~/.dsh/profiles/web/cordis.patch.yml`). Edit an existing entry with the same id instead of adding a duplicate. This profile layer is applied after the bundled configuration, so future plugin applies keep the override.
  269. ```yaml
  270. - id: bash-sandbox
  271. config:
  272. timeoutMs: 10000
  273. ```
  274. With the standard jobs service and `promoteOnTimeout: true`, an unfinished command returns a background job id after 10 seconds and keeps running. Read it with `job_output` or stop it with `job_kill`. This changes the foreground wait, not the command's speed. Without that service or with promotion disabled, the timeout kills the command. A per-call `timeoutMs` overrides this default; `run_in_background: true` returns a job id immediately.
  275. For routine tasks, you can also opt into Low reasoning for new sessions:
  276. ```yaml
  277. - id: agent-default-model
  278. config:
  279. provider: deepseek-official
  280. model: deepseek-flash
  281. reasoningEffort: low
  282. ```
  283. Restart `dsh web` to load the profile. The model and reasoning defaults apply to newly created sessions; select Low in the composer for an existing session. The plugin does not change these model preferences automatically. Keep High when the task needs deeper reasoning, and narrow file searches rather than recursively scanning every application directory.
  284. ### Own servers
  285. Attack tasks are denied by default. Only lab targets pass: localhost/private nets, known range platforms, and the one host registered first. Saying “this is my server” in chat does not allow it. A key or a password does not allow it either.
  286. The box sits under Prompt. If the dock does not show it yet, quit DeepSeek Harness completely and open it again.
  287. 1. Click **dsh-purge** beside the session title and stay on **Clean**.
  288. 2. Scroll past **Prompt**. **Own servers** is the next block.
  289. 3. Put one host on each line, in one of these forms:
  290. - `203.0.113.10` — one IP.
  291. - `my-vps.example.com` — one exact hostname. After you save, the addresses that hostname resolves to at lookup time are allowed too.
  292. - `alice@my-vps.example.com` — the account only identifies this form. It does not prove the machine is yours.
  293. 4. Click **Save list**. The list is written to `$DSH_HOME/net-scope-allow.txt`.
  294. 5. Keys, passwords, ranges, and wildcards are dropped on save. Unlisted public addresses stay forbidden.
  295. `203.0.113.10` and `example.com` above are only examples of the form. Replace them with your own host before you save.
  296. ---
  297. ## Local checks
  298. ```sh
  299. node --check lib/index.js
  300. node --check lib/core.js
  301. node --check lib/surface.js
  302. node --check lib/web.js
  303. node --check lib/desktop.js
  304. node --check lib/host.js
  305. node --check lib/rewind.js
  306. node --check lib/skills.js
  307. node --check client.js
  308. ```
  309. ---
  310. ## How it works
  311. Apply, on start or when you click Apply:
  312. ```mermaid
  313. flowchart TD
  314. A["Start or click Apply"] --> B{"Patch already in place?"}
  315. B -->|yes| C["Skip"]
  316. B -->|no| D["Back up the original as .dshpurge.bak"]
  317. D --> E["Replace the matched files"]
  318. E --> F["Override the shim"]
  319. F --> G["Inject the encrypted prompt shipped in the plugin, the text the prompt box shows by default"]
  320. ```
  321. Override on each session:
  322. ```mermaid
  323. flowchart TD
  324. A["Restart or new session"] --> B["Inject the plugin's encrypted default. No save click, and no host prompt file"]
  325. ```
  326. Prompt injection and ruleset decision at every turn. The three inputs on the left are what you control in the dsh-purge panel; the dotted edges show which decision each one drives:
  327. ```mermaid
  328. flowchart TD
  329. L["Rule library: activate a set → writes prompt-inject.md"]
  330. W["Local rules: check AGENTS.md / CLAUDE.md in the current dir"]
  331. P["Workspace policy: strict / fallback / always"]
  332. A["Turn start"] --> B{"prompt-inject.md non-empty?"}
  333. B -->|yes| C["Inject = prompt-inject.md (A)"]
  334. B -->|no| D{"Any checked local md in the current dir, non-empty?"}
  335. D -->|yes| E["Inject = selected workspace md (B)"]
  336. D -->|no| F["Inject = plugin encrypted slot default (D)"]
  337. C --> G{"Workspace baseline policy (C)"}
  338. E --> G
  339. F --> G
  340. G -->|strict| H["Drop DSH workspace baseline section"]
  341. G -->|fallback default| I{"User inject present above? (A or B)"}
  342. G -->|always| J["Keep DSH workspace baseline section"]
  343. I -->|yes| H
  344. I -->|no| J
  345. H --> K["Final system prompt"]
  346. J --> K
  347. L -.-> B
  348. W -.-> D
  349. P -.-> G
  350. ```
  351. Skills stay out of the inject section:
  352. ```mermaid
  353. flowchart LR
  354. A["Settings import or /skills import"] --> B["Write into the official skills directory"]
  355. B --> C["DSH loads it"]
  356. C --> D["Uninstall does not delete user skills"]
  357. ```
  358. ---
  359. ## Restore
  360. - Each target is copied to `<file>.dshpurge.bak` before the first apply.
  361. - **Restore** or `/purge revert` copies backups back and deletes them. With no backup, shim lines written by this plugin are stripped.
  362. - `prompt-inject.md` is a user file and is kept.
  363. - **Uninstall** restores first if patches were applied, then deletes the inject file, rule library, and the plugin itself.
  364. - Apply is idempotent.
  365. ---
  366. ## Path detection
  367. The host surface is detected first: `web` / `desktop` (`gui` / `tui` are reserved and still fall back to web).
  368. **Web:**
  369. 1. `DSH_HOME` / `DSH_BASE`
  370. 2. `.dsh` next to the dsh launcher (portable install, any drive)
  371. 3. `npm prefix -g` / `npm root -g`
  372. 4. Nested `@deepseek-ai/dsh/node_modules/@deepseek-ai`
  373. 5. `~/.dsh`
  374. **Official desktop EXE:** the running official Harness install (`resources/app` or the unpacked package). The drive letter is not hard-coded. A successful Apply restarts once.
  375. Community Desktop is not maintained.
  376. Official npm-global is not patched. Sealed `host-commands` / `runtime-commands` are scrubbed, never injected.
  377. If nothing is found, set `DSH_BASE` / `DSH_DESKTOP_INSTALL`. No files are changed.
  378. ---
  379. ## Releases
  380. The author's personal channel: [t.me/LLM_PoJia](https://t.me/LLM_PoJia). Notes and updates show up there. GitHub [Releases](https://github.com/YuJunZhiXue/dsh-purge/releases) still has older packages. The original may not be resold; forks must attribute.
  381. ## Notes
  382. - Scope is rendered copy, defaults, and runtime logic inside local `@deepseek-ai/*` packages, plus override files and rule sets under the harness home.
  383. - After an upgrade, unmatched originals show as skipped. Apply still completes, and those files are left unchanged.
  384. - Third-party plugin *source repos* outside `@deepseek-ai` are left alone (CMD silence may **best-effort** patch installed doctor / market / liangshen / mnemon at runtime).
  385. - Install from the GitHub archive (there is no npm package): `dsh plugin --profile web add https://github.com/YuJunZhiXue/dsh-purge/archive/refs/heads/master.tar.gz` (use profile `desktop` for the EXE). From this repo, `add .`.
  386. ---

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.