dsh-tool-result-guard
DeepSeek Harness (DSH) 的零损失工具结果裁剪：超大的工具结果会先溢写到文件，然后使用被省略区段的精确偏移量和恢复定位器进行裁剪。一个 dsh-plugin。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-tool-result-guard@0.1.0Tool Result Guard 以 dsh-tool-result-guard 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
点击下方 Badge 复制 Markdown，粘贴到 README 即可。
验证 package.json 声明的 GitHub 仓库，即可管理这个公开页面。认领后，Hub 会优先安排当前版本的安全扫描，并在通过后公开展示结果。
认领这个 Plugin →English | 中文
Zero-loss tool-result pruning for the DeepSeek Harness (DSH). A dsh-plugin.
Oversized plain-text tool results are spilled to a file first, then replaced with a bounded head/tail preview whose position-0 marker carries the exact elided span and the spill locator. The model can always recover the middle; nothing is ever dropped without a durable copy.
[pruned: kept chars [0, 4096) + [28976, 30000) of 30000; the elided middle
[4096, 28976) is NOT lost — full output saved at: /tmp/dsh-spill/.../bash.txt.
Recover any elided span with the read tool (offset/limit), grep, or sed on that file.]
<head: first 4096 chars>
[... middle elided ...]
<tail: last 1024 chars>
DSH ships two built-in mechanisms:
| mechanism | trigger | behavior |
|---|---|---|
dsh-spill-policy | result > maxInlineBytes (default 50000 bytes) at post-execute | full text to ctx.spillStore, bounded preview + locator returned — zero-loss |
dsh-compaction-tool-result-pruner | text > 8192 chars, only when compaction pressure qualifies | head 4096 + [... tool result middle pruned ...] + tail 1024. The original event stays in the append-only session log for replay, but the model gets no locator, no offsets, and no tool to read the log — the middle is unrecoverable for the model |
The gap: results between ~8K chars and 50K bytes that survive until compaction are pruned with no model-facing recovery path. This plugin closes the gap by pruning earlier (at tools/post-execute), always spilling the full text first, and embedding the exact elided span [head, total-tail) plus the locator in the marker.
If you install this plugin, the built-in pruner finds nothing over 8K chars on the surface and becomes a no-op; you may keep or remove its row. Same for spill-policy (its cap is never reached). Keeping both is harmless.
One command:
dsh plugin --profile web add dsh-tool-result-guard
Restart DSH. Done — it now applies to every agent preset in that profile. Remove with dsh plugin --profile web remove dsh-tool-result-guard.
Tune the budgets by id in your profile's ~/.dsh/profiles/web/cordis.patch.yml:
- id: tool-result-guard
config:
thresholdChars: 16384
npx dsh-tool-result-guard install --preset my-preset --from standard
copies the shipped standard preset to ~/.dsh/.agent-presets/my-preset/, drops dsh-tool-result-guard.js beside its agent.cordis.yml, and appends the plugin row; start a new session on my-preset. Patch an existing user preset with --preset <id> (no --from), undo with remove --preset <id>, print the snippet with --print. Manual equivalent — copy index.js next to the preset's agent.cordis.yml and append:
- id: tool-result-guard
name: './dsh-tool-result-guard.js'
Unknown keys fail at load. All budgets are Unicode code points (surrogate pairs never split).
| Key | Default | Meaning |
|---|---|---|
thresholdChars | 8192 | Prune when the flattened plain-text result exceeds this many code points. |
headChars | 4096 | Leading code points kept inline. |
tailChars | 1024 | Trailing code points kept inline. |
excludeTools | ["read"] | Tools whose results always pass through. read is excluded by default to prevent a read spill file → prune → read again loop. Add e.g. ["read", "subagent", "memory_search"]. |
spillDir | (unset) | Override the local fallback spill directory (default: a private dir under the OS temp dir). |
headChars + tailChars must be below thresholdChars so the marker always fits.
ctx.spillStore when loaded, else a private per-process local directory) before the middle leaves the model-facing result.tools/post-execute waterfall listener and delegates via next(), so tool-owned projection and other hooks run first; their replaced content is what gets pruned. additionalContexts survive.thresholdChars, so a second pass never re-prunes.The marker names the spill file and the exact char span. Models recover with read (offset/limit), grep -n, or sed -n 'X,Yp' on that file — the read exclusion prevents recovery reads from being pruned themselves.
npm test # node:test, zero dependencies
MIT