dsh-system-prompt-editor
编辑注入每个新会话系统提示词中的文本块
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:n0pe-sled/system-prompt-editor#9e4ff88d7e064e738d3fdf1490ecebef378d3f87System Prompt Editor 以 dsh-system-prompt-editor 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A dsh plugin that edits the system prompt of every new session on this machine from the Settings page. Every stable section of the assembled prompt is editable — the harness identity, the source-checkout line, the web-surface orientation, the persona, the file-reference note, the tool-guidance prose band, the deliverables note, and the custom tail — plus third-party sections discovered through a preview.
| Field | Band | Effect when non-empty |
|---|---|---|
| Harness identity | order −100 | Replaces the fixed identity opener. |
| Source checkout | order −99 | Replaces the harness source-checkout line. |
| Web surface | order −98 | Replaces the web-surface orientation section. |
| Persona | order 0 | Replaces the deployment persona section. |
| File-reference note | order 99 | Replaces the note about mentioning created/modified files. |
| Tool guidance | orders 100–199 | Replaces the per-tool guidance prose sections with one section. |
| Deliverables note | order 190 | Replaces the response-format note about mentioning primary outputs. |
| Custom system prompt text | order 200 | Appended verbatim after the persona and tool guidance. |
All overrides are evaluated/applied at every assembly, so a save takes effect on the very next request. No restart needed.
Blue-banded sections in the preview — Plan mode policy, Code-mode rule, and Code SDK guidance — are owned by DSH state or code-mode plugins and are shown read-only ("Managed by DSH"): they are functions of agent state, and overriding them would fight their owning plugins.
| Action | Behavior |
|---|---|
| Save | Persists the draft into the system-prompt-editor settings namespace. Confirms with "Saved", or reports when the write did not land (host-side refusal / revision conflict) and keeps the draft so nothing is lost. |
| Preview system prompt | Shows the entire assembled prompt as the model would see it — every section, with the current drafts applied — annotated per band, with DSH-managed sections marked. {{model}}/{{provider}} resolve from the real default-model selection; references with no scope-less value (like {{cwd}}) render literally instead of erroring. Third-party sections seen in the preview become editable cards (generic per-section overrides). |
| Load current system prompt | Fetches that section's current effective text with a fresh host-side assembly (no drafts) and loads it into the editor — the stored override when one exists, otherwise the deployment default — so the textarea holds what the model actually reads today, ready to edit and save. Saving the loaded default stores it as a fixed override; clearing back to empty restores the default. |
While the settings scope is loading, the actions are disabled; in a remote (non-loopback) browser the page shows a note that settings are process-local and stays inert. Empty stored values leave the deployment defaults untouched, so clearing a field restores the original prompt without the plugin ever knowing what it was.
From the directory that contains system-prompt-editor/:
dsh plugin --profile web add ./system-prompt-editor
(First use of dsh plugin initializes the profile with
@deepseek-ai/dsh-base.) The bundle layer is appended because the manifest
declares dsh.bundle; the same patch row also puts the package on the web
client roster (dsh.client.platform: "web"), so the Settings page appears
without extra wiring. If dsh is not on your PATH, run the same command as
pnpm dsh ... from a dsh source checkout, or node <dsh-install>/bin.js ....
The registry serves lib/client.js, not sources — rebuild and restart the
host after changing either half (the host half loads at boot):
pnpm build
# restart the web GUI: the host half of a running instance keeps its boot-time code
system-prompt-editor namespace of the settings document,
machine-global like every dsh setting. Under the shipped file provider this
is $DSH_HOME/settings.yaml (section system-prompt-editor: with text:,
persona:, toolGuidance:, and a sections: map keyed by section name,
e.g. harness:identity: "..."). Saved text survives restarts and is shared
by every profile on the machine.src/shared/catalog.ts pins the editable/read-only
section names, canonical orders, labels, and warnings of the dsh release
this build targets; both halves bundle it. The UI renders one card per
curated entry; the host uses it for band chips and for inserting a section
that is absent from a given assembly at its canonical position.user:system-prompt-editor) at configurable order (default 200: after
the deployment persona at 0 and tool guidance at 100–199). Empty text
yields an empty section, which assembly drops — no custom text costs zero
tokens. {{name}} variable references (e.g. {{cwd}}, {{model}},
{{provider}}) resolve at request time like any other section.system-prompt/assemble waterfall listener
(src/shared/overrides.ts, shared with the preview) replaces the
deployment:persona text (order 0), collapses the tool prose band
(orders 100–199) into one user:tool-guidance section at order 150, and
applies every non-empty sections[name] entry — replacing the assembled
section of that name in place, or inserting it at its catalog order when
absent (per-agent sections like the file-reference note, which register
scoped, are replaced in real sessions and only appear as insertions in the
scope-less preview). Tool schemas are never touched; empty stored values
leave the defaults alone.systemPromptEditorPreview/preview) assembles the full prompt host-side
(stored values flow through the waterfall), applies the drafts, and renders
leniently ({{model}}/{{provider}} come from the real default-model
selection; any other unresolved reference stays literal — a stock web
persona references {{model}}/{{cwd}}, and {{cwd}} is only knowable
per session), returning { rendered, sections, effective }. The client
mounts the same descriptor and unwraps the . The preview
assembles without a specific agent, so per-agent presets may differ (noted
in the UI caption); per-agent sections absent from a scope-less assembly are
shown as inserts in their canonical band. The per-tool guidance sections
register per agent too — the waterfall listener snapshots them from every
real assembly, and the preview replays that snapshot in-band, which is also
what the tool-guidance card's Load fills when nothing is stored.request/header, so the runtime-cached provider-prefix reuse
is invalidated from the first changed token — inherent to the feature.harness:identity,
harness:source, or app:web-surface removes orientation the harness
depends on; the UI marks those cards accordingly, as it does for the
file-reference note (which is what makes changed-file links clickable).dsh 0.1.1-rc.2 (see src/shared/catalog.ts); bump the pin and review
the catalog when upgrading the harness. Newer dsh split the persona into
prefix/suffix sections — the catalog recognizes those names for the persona
band but does not add overrides for them.dsh --profile web --dump-config # shows a "# == dsh-system-prompt-editor" layer
node tests/smoke.mjs # host-half smoke check (needs `pnpm build` first)
node tests/integration-real.mjs # real providers (dsh-system-prompt + dsh-settings-file in a temp dir)
Then open the web GUI → Settings → System Prompt: edit, Save, check
$DSH_HOME/settings.yaml (the sections: map gains your keys), start a fresh
session and ask the model about its system prompt, or export the session log
and inspect the model-visible messages. Load current system prompt must
round-trip per field; clearing a field must restore the deployment default.
pnpm install # devDependencies (cordis, schemastery, client type packages, tsdown, typescript, react)
pnpm typecheck # tsc --noEmit
pnpm build # tsdown: lib/index.js (node half) + lib/client.js (browser half)
node tests/smoke.mjs # host-half smoke check against stubbed services
prepare also runs tsdown, so a git install builds itself (pnpm ≥ 10 asks
you to allowlist the build script in the profile's pnpm-workspace.yaml).
RemoteResultorder: 200 in the plugin row config (profile
cordis.patch.yml or a --patch overlay) moves the custom section; the
schema default is 200.