dsh-loop-rescue
在流式生成过程中中断模型重复循环，从已提交的消息中移除循环内容，并自动继续生成的 DSH 插件。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:citydirector/dsh-loop-rescue#b3a5c90d32a73fb1555fbac8fc2cdd830af1d011Loop Rescue 以 dsh-loop-rescue 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A loop-rescue plugin for DSH (DeepSeek Harness). When the model falls into repetition (Now. / OK. / Emit. / Producing. rotations, the same paragraph over and over), it cuts the stream from the inside, prunes the loop out of what gets written to the session log, and resumes automatically.
The difference from a plain cut-off: the interrupted message that goes into the next turn's context contains no loop, so the model never re-reads its own repetition and carries on repeating.
Requires DSH 0.1.7 or newer. Pure JS, no build step.
Use this or @mrweicodes/dsh-loop-guard, not both: with both on, loops get cut twice.
https://github.com/citydirector/dsh-loop-rescue
mode to observe (see Configuration).From the command line:
dsh plugin --profile web remove @mrweicodes/dsh-loop-guard
dsh plugin --profile web add -w github:citydirector/dsh-loop-rescue#v0.1.0
Restart dsh web after a command-line install. No pnpm build scripts need approving.
The defaults work as they are. To change them, write to the profile's cordis.patch.yml:
- set:
- id: loop-rescue
config:
mode: rescue # rescue: cut + prune + resume | cut: cut + prune | observe: log only
watch: both # both | reasoning | text
marker: true # leave a "〔N chars of repeated reasoning removed〕" line where it pruned
maxConsecutiveRescues: 3 # cap on back-to-back rescues; one normal call resets it
stallCalls: 3 # nudge after this many reasoning-only calls with no output; 0 = off
stallMinReasoningChars: 1024
retryTemperature: 1.0 # temperature for the resume request; unset = unchanged
retryReasoningEffort: low # reasoning effort for the resume request; unset = unchanged
retryRequests: 1 # how many requests after a resume use the two settings above
language: auto # auto | zh | en
detector: # detection thresholds; rarely need changing
poolWindow: 30
poolMinCoverage: 0.75
cycleMinChars: 600
Consider running mode: observe for a day or two first, check that every loop-rescue: ... loop detected line in the log is a real loop, then switch to rescue.
When the agent loop assembles an assistant/message, each block's final content comes from the block-end payload, not from the deltas streamed before it. The plugin wraps the model call in the llm/stream waterfall:
stop.stream record, where the trajectory view can show it.whenIdle()), it sends a resume message with a correction via followup().Why not edit the session afterwards: an assistant/message cannot carry sourceEventSeqs, so the session surface's replace operation cannot swap one assistant message for another. Pruning at block-end is the only way that keeps message roles and tool-call pairing intact.
| Rule | Catches | Prunes from |
|---|---|---|
Phrase pool pool | ≥75% of the last 30 sentences are a handful of recurring short phrases (in any order) | Back to where that batch of phrases first appeared |
Verbatim cycle cycle | The tail is the same text repeated verbatim, period 16–4000 chars, ≥3 repeats, ≥600 chars in total | Keeps the first copy, prunes from the second |
Guarding against false positives:
|---|, }) are not counted.Replay past sessions through the same detector the plugin uses, to see where it would cut:
node tools/scan-session.mjs <session file or directory> # hits only
node tools/scan-session.mjs <session file or directory> --all # hits and misses
node tools/scan-session.mjs <session file> --json
Reads plain jsonl and zstd-compressed session files (zstd needs Node 22.15+). The script only depends on src/detector.js and runs on plain node.
The plugin only stops new loops; loops already committed to the history keep being imitated by the model. What DSH sends the model is a frozen projection of the session log, which a plugin cannot change, so the session files have to be cleaned offline with DSH fully closed. This works for old sessions that never had the plugin too.
The recommended tool is dsh-session-manager (dsm loops, a single-file exe on Windows): the same detection rules, plus upgrading, archiving and repairing broken sessions.
This repository also ships a lightweight script (Node 22.15+, v4 sessions only):
node tools/clean-session.mjs # list sessions with loops, pick by number; Enter = newest
node tools/clean-session.mjs --dry-run # show what would change
node tools/clean-session.mjs --undo # restore from the backup
tools\clean-session.cmd, or drop a session folder onto it; if it cannot find the data directory, pass --data <data directory>.assistant/message events change: text and reasoning are cut back to where the loop started, data.stream is cut to match, and the message's source.replayState is removed. Every other line stays byte-for-byte the same.<data directory>\sessions-loop-rescue-backup\ first, and refuses while DSH is running (--force skips that check; not recommended).dsm repair brings hidden sessions back.guard/repeat-tool-reminder.retryTemperature needs an adapter that supports temperature. DSH has no generic field for Ollama's repetition penalty and similar parameters, so they cannot be set from here.npm install
npm test