dsh-temperature-picker
DeepSeek Harness 插件：位于模型选择器左侧的温度选择按钮——带刻度的滑块（0–1.2，步长 0.1）及范围校验输入框，通过 agent/request 流程应用于每个提供商，并通过 profile patch 持久化。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-temperature-picker@0.1.0
Temperature Picker 以 dsh-temperature-picker 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 中文
A DeepSeek Harness plugin that adds a temperature picker button right next to the model selector (on its left) in the composer. Click it to open a panel with a ticked slider (0–1.2, step 0.1) and a range-checked numeric input, tuning the temperature of every model call.
cordis.patch.ymltemperature, follows the provider default)Requires DeepSeek Harness (tested on v0.2.1-rc.3).
npm (once published):
dsh plugin --profile web add dsh-temperature-picker
GitHub:
dsh plugin --profile web add github:ChurSu/dsh-temperature-picker
Desktop app (the desktop profile is owned by Electron; use the bundled CLI):
"<install-dir>\resources\runtime\cli\bin\dsh.cmd" plugin --profile desktop add dsh-temperature-picker
Or use the in-app Plugins page. Refresh the page (or restart the app) after installing; a「温度」/ temperature button appears at the bottom-left of the composer.
Both halves follow DSH's "everything is a plugin" composition:
index.js): declares a volatile temperature config field and merges it into every LlmCallConfig inside the agent/request waterfall (the legal mutation point before requests are frozen). When unset, it actively deletes temperature from the config — necessary because the agent loop starts subsequent requests from the folded request/header snapshot, where a previously injected value would otherwise stick (this plugin owns the field).client.js): registers into the conversation.input.right slot (rendered immediately left of the model selector) and reads/writes the host entry's volatile field through ctx.remote.settings.describe/mutate; writes persist through the settings/config-editor into the profile's cordis.patch.yml.Changing temperature is an envelope change: a new request/header (reason: change) is logged and a new request series begins; message history is unaffected.
temperature at all — behavior is identical to not having the plugin.dsh-temperature-picker/
├── index.js # Host: volatile config + agent/request injection
├── client.js # Client: composer button + slider panel (plain React.createElement, no build step)
├── cordis.patch.yml # Bundle layer: inserts the plugin row into the profile
├── package.json # dsh.bundle / dsh.client declarations
└── assets/ # Docs screenshots
Debugging tip: the request/header event in a session log carries config.temperature — exactly what the model received ("model-visible means logged").