AI Agent Hub
Back to plugins
🖥️

dsh-turn-doctor

Client Updated 2026.09.03

Run the following command in DeepSeek Harness:

dsh plugin install d3vmeh/dsh-turn-doctor

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install d3vmeh/dsh-turn-doctor in the DeepSeek Harness terminal to install; the plugin source is available at https://github.com/d3vmeh/dsh-turn-doctor .

About this plugin

A dsh request can stall at any of several layers - its own idle watchdog, the SDK timeout timer, undici HTTP timers, the model server, or an individual tool call - yet the terminal usually only prints one vague error message, making it hard to tell which parameter to change. dsh-turn-doctor is a diagnostic plugin built for exactly this pain point.

It measures every model request itself (time to first byte, longest inter-byte gap, total duration) and cross-references those timings against known failure signatures to pinpoint the most likely culprit: undici 300-second headers timeout, SDK timeoutMs, queue timeout, context overflow, tool-call timeout, or a crashed server. Each retry is diagnosed independently; when the timing is too ambiguous to distinguish two causes, it says so rather than guessing.

Ideal for dsh users who juggle multi-model routes, parallel subagents, or heavy tool workflows and keep hitting timeouts without knowing which setting to touch. After installation no extra configuration is needed - verdicts print straight into the terminal, and the /why chat command surfaces recent diagnostics for the current session.

Use Cases

  • Repeated timeouts with vague terminal errors make it unclear which timeout parameter to adjust
  • Ambiguous timeout errors across multi-model routes or parallel subagents need to be disambiguated between SDK, undici, and server layers
  • Tool-call timeouts or failed compactions need quick identification of which layer triggered them

Best For

  • Developers who use the dsh CLI daily
  • dsh users running multi-model routes or parallel subagents
  • dsh users who hit timeouts repeatedly and are unsure which setting to change