Skip to content

dsh-dsml-rescue

Verified

dsh-dsml-rescue · v0.3.0 · MIT

Auto-continues turns stalled by DSML tool-call markup leaking into reasoning.

Install

dsh plugin add dsh-dsml-rescue

Confirm the layer applied with dsh --profile default --dump-config — see the install guide.

Source

Tags

Readme

dsh-dsml-rescue

dsh-dsml-rescue

A stalled turn gets another one

空转的轮次,替你续上

powered by dsh

CI npm MIT License

Per-version changes → Releases

English · 简体中文


Does this look familiar?

You asked for something. The model reasoned for a while. Then the turn simply ended — no answer, no tool call, nothing. The reasoning output ended with lines like these:

</||DSML|| parameter>
</||DSML|| invoke>
</||DSML|| calls>

DSML (DeepSeek Markup Language) is how DeepSeek formats a tool call. Some provider routes hand that markup back as ordinary reasoning text instead of an actual call, so the call never happens, the turn closes with no output, and everything waits for someone to type "continue".

This plugin types it.

What it does

  • Continues a stalled turn: DSML markup at the end of the reasoning, and nothing else produced. Neither half alone is enough — an empty turn without the markup is a different failure.
  • Sends one short, neutral line — carry on, or wrap up if the work is done.
  • Backs off while you are typing.
  • Gives up after a few attempts instead of burning requests.
  • Covers subagents too, so a delegated task is not falsely reported as completed while it is stuck.

Install

dsh plugin --profile web add dsh-dsml-rescue

Then restart dsh --profile web. There is nothing you need to configure — the defaults are the intended behaviour.

Working from source: clone, pnpm install && pnpm run build, then dsh plugin --profile web add "$PWD".

What it will not do

  • It does not fix the cause. The markup leaks below the model, out of reach of any prompt. What it buys you is the wait, shortened.
  • It does not rescue other empty turns. No DSML markup, no rescue: a cancellation, a failed request, or a reply cut off at the output limit is left alone on purpose.
  • It does not touch your conversation. Nothing is rewritten or replayed; it adds one message and lets the host carry on.

Going deeper

License

MIT