dsh-user-preferences
DeepSeek Harness 插件：将你的固定偏好设置（全局及每个项目的 Markdown 文件，支持热加载）注入每个请求。避免启动时依赖可选服务，并在偏好设置出错时继续运行。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:Alan-IFT/dsh-user-preferences#9b8a3e92ccda7ecaf3570f170e8cd5279e87b226User Preferences 以 dsh-user-preferences 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Replacement for dsh-user-prompt. Injects your standing preferences into every model request.
The host half avoids coupling to the settings service and handles optional-service and file errors without failing prompt assembly. A malformed package or missing hard dependency can still prevent activation.
| File | Scope |
|---|---|
<dshHome>/preferences/global.md | all sessions (dshHome = $DSH_HOME or ~/.dsh) |
<project>/.dsh/preferences.md | nearest to the session cwd; walks up, stops at the repo root (.git) or ~ |
<dshHome>/preferences/settings.json | { "enabled": true, "mode": "section" | "context" }, overrides plugin config live |
Project text takes priority over global text when the budget (maxChars, default 20000) is exceeded.
<!-- html comments --> are stripped, so you can leave notes to yourself.
section (default): merged into the system prompt (highest authority); {{...}} stays literal.context: separate user-role snapshot; every {{ is defused so the renderer cannot throw.systemPrompt is a hard dependency; commands / connection are attached lazily via ctx.inject.settings service; invalid settings-file values fall back at runtime.apply()./preferences shows the status. /preferences path prints the global file path.
package.json, pnpm-lock.yaml, pnpm-workspace.yaml and cordis.patch.yml and copy the old prompt to <dshHome>/preferences/global.md.link:D:/Programs/dsh-user-preferences; include dsh-user-preferences in dsh.profile.bundles and remove dsh-user-prompt from both dependencies and bundles. Remove its user-prompt row from cordis.patch.yml without changing unrelated rows.user-preferences and not user-prompt, then confirm the Plugins → User preferences card loads and saves, and prompt assembly contains the migrated text. The generated cordis.yml can remain unchanged after a live HMR reconciliation; its timestamp alone does not prove whether the running Host reloaded.The link: spec uses the local source directory. Keep that directory intact while installed. Revert the backed-up profile files and reinstall its dependencies to roll back; do not overwrite the migrated global preferences file.
node --test test/core.test.mjs test/client.test.mjs test/rpc.test.mjs
node test/host-integration.mjs # requires extracted host packages in .tmp/host