dsh-highlightpin
DeepSeek Harness 的三级源文本固定项：召回内容、常驻背景和突出显示的约束。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-highlightpin@0.1.2Highlightpin 以 dsh-highlightpin 发布，当前版本为 0.1.2。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Pin any selected passage; compaction cannot take it away.
中文 · Design · Evaluation · Live evidence
A DeepSeek Harness (DSH) plugin. Select any stretch of text in a conversation — a constraint, a number, a formula, a piece of code — and pin it with one click. From then on, no matter how the context is compacted, what the model receives is that source text, not a summary.
Each pin carries its own level:
| Level | Behaviour | Good for | Cost |
|---|---|---|---|
| pin (default) | Does nothing while the text is still in context; once compaction drops it, the extract text is re-inserted verbatim near the tail before the next request | Most pins | Never touches the system prompt, so it does not break the prefix cache on its own |
| resident | Lives in the system prompt with neutral wording: "consult it when relevant; no need to bring it up" | Important background: you want the model to match on it the moment it matters, without you mentioning it every turn | Costs one prefix-cache invalidation when you switch levels |
| highlight | Lives in the system prompt with emphatic wording: "follow it when relevant; if it conflicts with your latest explicit instruction, the latest instruction wins" | Constraints and priorities the model must keep honouring | Same as above; emphasis also raises how often the model brings it up on its own |
resident and highlight are deliberately two separate levels. "The model can always find it" and "the model always keeps it in mind" are different things, and emphasis has side effects of its own — so the choice is yours.
From npm (published releases):
dsh plugin --profile desktop add dsh-highlightpin@0.1.2
Or straight from the GitHub source:
dsh plugin --profile desktop add 'https://codeload.github.com/sbearbug/dsh-highlightpin/tar.gz/v0.1.2'
On the web profile, replace desktop with web. After installing or upgrading, fully quit and restart DSH, then refresh the page, so that host and client both load the new version. Existing pins survive.
peerDependencies declares >=0.1.7-rc.1 <0.2.0-0 || >=0.2.0-rc.1 <0.3.0-0. The DSH plugin manager checks these peers with semver.satisfies(runtimeVersion, range, { includePrerelease: true }) and blocks installation and activation on a mismatch.
The range carries an explicit prerelease branch on purpose: under ordinary semver semantics a single >=0.1.7-rc.1 <0.3.0-0 does not match the 0.2.0-rc.* builds, because node-semver admits a prerelease only when some comparator in the range shares its exact major.minor.patch tuple and itself carries a prerelease tag.
| DSH version | Status |
|---|---|
| 0.2.0-rc.2 | Verified live — development and real-machine checks both ran on this version |
| 0.1.7-rc.1 / 0.1.7-rc.2 | Offline suite passes; CI re-runs the same suite against this line on every push |
| Other 0.2.x | Inferred from the APIs used, not verified individually |
| ≤ 0.1.6 | Unsupported: CommandDefinitionId does not exist at 0.1.5 and below, and the 0.1.6 line's session-event validation already differs |
| ≥ 0.3.0 | Not claimed |
When you select inside a formula, the selection is expanded to the whole formula and what gets stored is the TeX source. Select the rendered $\nabla_\theta J(\theta)$ and the plugin stores $\nabla_\theta J(\theta)$ — not the glyphs on screen. Selections inside code keep their indentation and line breaks.
Everything is also available from the command line:
| Command | Effect |
|---|---|
/hlpin list | List every pin, its level and budget usage |
/hlpin last | Pin the most recent assistant reply in full |
/hlpin show <n> | Show one pin's full text |
/hlpin drop <n> | Unpin |
/hlpin level <n> pin|resident|highlight | Change a pin's level |
source-exact (a clean hit), source-normalized (matched after whitespace and Markdown normalisation, but still storing a source slice), or rendered (no match — it stores the display text and tells you so).pin only re-inserts after the original is gone. Right after pinning, the text is already in context, so re-injecting it would be pointless. It comes back only once compaction has shadowed it — and at that moment the prefix cache was already invalidated. So the default level cannot break caching by construction.pin, resident and highlight each have their own character pool. Adding or promoting past a pool's budget is rejected outright with an error code; demotion is always allowed. The plugin never quietly truncates, evicts, or demotes a pin.storageDomain, and recall uses a message type the host already has, so a session can never become unloadable from an unknown event. The HTTP API is origin-checked and accepts JSON only from the local page.The full set of trade-offs is in DESIGN.md.
/compact → next message" has been run end-to-end in DSH. The shadowed source text appeared in the next request's input, byte-identical to what was stored, with a matching SHA-256. Evidence: docs/PROBES.md and docs/m1-live-0.1.4.json.{ "maxPinChars": 16000, "maxResidentChars": 6000, "maxHighlightChars": 2000, "holdSubagents": false }
| Setting | Default | Meaning |
|---|---|---|
maxPinChars | 16000 | Total source characters across pin pins |
maxResidentChars | 6000 | Total source characters across resident pins |
maxHighlightChars | 2000 | Total source characters across highlight pins |
holdSubagents | false | Whether subagent sessions are covered too (off by default, to avoid wasting tokens) |
Characters are counted in UTF-16 units. Neither the number of pins nor the length of a single pin is capped; only the total per level is.
npm ci
npm run check # build the client + run all tests + loader check
npm run eval # controlled fixture: byte-exact preservation through all three levels
MIT