dsh-system-prompt-studio

dsh-system-prompt-studio

A [DeepSeek Harness](https://github.com/deepseek-ai) plugin that lets you inspect and override the

system prompt a conversation actually sends to the model — per conversation, at runtime, without

restarting.

> **This plugin ships as the scoped npm package

> [@user-mrz/dsh-system-prompt-studio](https://www.npmjs.com/package/@user-mrz/dsh-system-prompt-studio).**

> An unrelated, unscoped package named dsh-system-prompt-studio also exists on npm, maintained by

> someone else. Installing that one will not give you this plugin. Always install the

> @user-mrz/-scoped name.

DSH itself only exposes deployment-wide persona prefix/suffix in configuration files: change one and you

need a restart, and it affects every session. This plugin moves the same capability to runtime, per

session, effective immediately.

> 中文说明见文末 · [跳转到中文](#中文说明)

---

What it does

• See the real thing. The panel shows the system prompt your conversation actually sent on its

last request, plus the section list that was assembled for it (name / order / character count).

• Override it three ways.

| Mode | Effect |

|---|---|

| Append (default) | Keeps every first-party section, adds yours at the end. Safest. |

| Replace a section | Shadows one named first-party section, e.g. deployment:persona-suffix. |

| Replace everything | Your text becomes the entire system prompt. Highest risk — see below. |

• Applies on the next model request. No restart, no reload.
• Persists per session, and a global default applies to new conversations automatically.
• Inherits across forks. A forked conversation picks up its parent's rules along the parentSession

chain, with a Pin action to freeze the inherited result locally.

• Guards unsaved edits. Esc, backdrop click and the close button all ask before discarding.
• Zero runtime dependencies. Only Node built-ins; it does not import any @deepseek-ai/* package.

⚠️ Before you use "Replace everything"

That mode removes all first-party guidance — tool instructions, structured-output rules, plan-mode

policy. Tool-calling quality can drop noticeably. Runtime context (working directory, sandbox policy,

approval policy) is still sent as a user-side snapshot and is not replaced by your text.

Also: assembly allows only one active complete section. If another plugin registers one in the same

session, assembly fails with multiple complete prompt sections. Switch back to Append or Replace to

recover.

---

Requirements

• DSH >=0.2.2-0 <0.3.0-0 (Web and Desktop share the same client artifact)
• Node.js ≥ 22.19.0

Install

The package lives at [npmjs.com/package/@user-mrz/dsh-system-prompt-studio](https://www.npmjs.com/package/@user-mrz/dsh-system-prompt-studio).

Install that scoped name — dsh-system-prompt-studio without the scope is a different author's package.

From npm (recommended — this is the version that gets version numbers, tags and a published tarball):

dsh plugin --profile  add @user-mrz/dsh-system-prompt-studio

From GitHub, which tracks the default branch and therefore needs a ref if you want a fixed version:

dsh plugin --profile  add github:user-Mrz/dsh-system-prompt-studio#v0.1.9

Replace ` with your profile name — for the Web build that is usually web`.

Pin a version for reproducibility. Without one you get whatever is newest, so a later release

changes what you install next time:

dsh plugin --profile  add @user-mrz/dsh-system-prompt-studio@0.1.9

Local directory install (for development)

dsh plugin --profile  add file:/absolute/path/to/dsh-system-prompt-studio

If pnpm blocks the build script

pnpm refuses to run build scripts from Git dependencies by default. This plugin's prepare script only

verifies that the entry files exist — it compiles nothing and writes nothing — so being blocked does