Back to directory

dsh-auto-continue

In a curated listMaintenance: Active

hsiangnianian/dsh-auto-continue

请求被网络错误等非人为原因中断时自动发送『继续』,避免手动重发;npm 已发布(dsh-client-auto-continue),安装后重启 dsh web 生效

View on GitHubHomepage
$ dsh plugin --profile web add dsh-client-auto-continue@latest

207

stars

26

forks

JavaScript

Language

MIT

License

2026-08-14

Created

2026-11-20

Last push

MIT-licensed DSH web UI plugin that runs in the host, retries transient failures with backoff, and exposes per-session modes, guards, and settings under Plugins → dsh-client-auto-continue.

DSH integration

Native runtime

Author-claimed

Safety audit

Unaudited

Last verified

2026-11-20

License

MIT

01What can it help you accomplish?

  • Recover an interrupted DSH turn without retyping continue

    Automatic continue messages after recoverable errors, output limits, silent turns, or a host restart cut-off

    People running long agent sessions in `dsh web` who do not want to babysit every failure

  • Keep one conversation going after normal completions when you opt in

    Autonomous loop rounds with an optional limit, plus loop-guard restarts when the model repeats itself

    Power users who want hands-off multi-turn work inside a single session

  • Pick up work after closing the browser tab or restarting the host

    One shared host-side engine across tabs, with startup recovery for sessions interrupted within the last 15 minutes

    DSH users who rely on the host staying alive after the UI disconnects

02How to install into DeepSeek Harness

Prerequisites

  • A DSH installation with the `web` profile — `dsh web` uses that profile
  • Desktop app users should install from the app **Plugins** page instead of the CLI

Installation steps

  1. 01

    Run `dsh plugin --profile web add dsh-client-auto-continue@latest`

    $ dsh plugin --profile web add dsh-client-auto-continue@latest

  2. 02

    Run `dsh web` if the web UI is not already up

    $ dsh web

  3. 03

    Restart DSH and reload the browser after installing

  4. 04

    Open **Plugins → dsh-client-auto-continue** in the sidebar and confirm status is **Running**

Verify the integration

  • In the sidebar, open **Plugins → dsh-client-auto-continue** and confirm it shows **Running**
  • Run `dsh --profile web --dump-config | grep -A 4 'id: auto-continue'` — the composed config should list exactly one `auto-continue` entry

Rollback

  • Run `dsh plugin --profile web remove dsh-client-auto-continue`
  • If present, remove the top-level `- id: auto-continue` block from the profile `cordis.patch.yml`, then restart DSH

03DSH integration and capability boundaries

DSH integrationNative runtime

CLI users add `dsh-client-auto-continue@latest` to the `web` profile with `dsh plugin --profile web add …`; desktop users install from the app **Plugins** page (separate profile). After restart the engine runs in the host and hooks session events.

  • Recoverable error retry

    Turn failures classified as transient (network, timeout, HTTP 5xx or 429)→Delayed continue message after grace period, cooldown, and adaptive backoff

    Sends a user-visible continue via `agent.followup`May append idempotency-guard notes about the last tool call
  • Per-session mode switch

    Composer toggle next to the message box→Follow default, Off, Recovery only, or Autonomous loop for the current conversation

    Persists `sessionModes` on the host immediately and syncs across tabs
  • Idempotency and loop guards

    Last tool-call outcome when a continue is sent; running turns watched for repetitive text or identical tool calls→Idempotency guard only appends text so the model knows whether the last tool call finished—it does not cancel or block tools. Loop guard cancels a repeating running turn and restarts it with loop text

    Idempotency-guard notes ride on continue messages sent via `agent.followup`Loop guard may call `agent.cancel` before restarting with loop text
  • Settings UI and notifications

    Edits under **Plugins → dsh-client-auto-continue**→Saved profile config, daily stats, recent recovery log, optional browser notifications

    Writes `auto-continue` config into the active profile patch (for example `~/.dsh/profiles/web/cordis.patch.yml`)Browser notifications request permission the first time you enable them
  • Host startup scan

    Sessions interrupted within the last 15 minutes when the host starts (default `freshMs` / scan window)→Resumes eligible open or stored sessions within the configured scan window

    Reads session history through DSH services during the scan (bounded read budget on large profiles)

04Who is it for? When not to use it?

Good for

  • People running long agent sessions in `dsh web` who do not want to babysit every failure
  • Power users who want hands-off multi-turn work inside a single session
  • DSH users who rely on the host staying alive after the UI disconnects

Not for

  • DSH 0.1.0-rc.6 and earlier hosts are not supported.
  • Plugin builds must pass DSH runtime version checks — for example 0.11.9 and 0.12.0 are rejected on DSH 0.2.0-rc.1; match the README compatibility table to your `dsh --version` runtime.
  • Continue messages and loop-guard cancellations act on your behalf through `agent.followup` and `agent.cancel`, keeping the session's existing tools and permissions.

05Compatibility, maintenance and safety notes

  • DSH 0.1.0-rc.6 and earlier hosts are not supported.
  • Plugin builds must pass DSH runtime version checks — for example 0.11.9 and 0.12.0 are rejected on DSH 0.2.0-rc.1; match the README compatibility table to your `dsh --version` runtime.
  • Continue messages and loop-guard cancellations act on your behalf through `agent.followup` and `agent.cancel`, keeping the session's existing tools and permissions.
  • When **Pause while offline** is on, the host inspects local interfaces and performs DNS lookups of `api.deepseek.com`, `www.baidu.com`, and `one.one.one.one` without opening connections.
2026-08-142026-11-17v0.20.2

MIT · last push 2026-11-17 · release v0.20.2

06Frequently asked questions

Which DSH runtime versions does the README verify?

The compatibility table lists pairs such as DSH 0.2.2-rc.1 with plugin 0.20.2 and DSH 0.2.0-rc.1 with plugin 0.12.1 or newer. DSH 0.1.0-rc.6 and earlier are not supported. Check `dsh --version` for the CLI runtime — the desktop app version is not the same number.

How is the web profile install different from the desktop app?

CLI users add the npm package to the `web` profile with `dsh plugin --profile web add dsh-client-auto-continue@latest`, then restart DSH. The README says desktop users should install and update from the app **Plugins** page, which uses its own profile.

What does the plugin read, store, or send?

It runs inside the DSH host, reads session events and history through DSH services, and does not contact third parties or store credentials. Settings land in the profile patch; retry counters and stats stay in memory. Optional offline checks only DNS-lookup public names without opening connections.

When should I avoid Autonomous loop mode?

Recovery only handles errors, limits, silent turns, and restart interruptions. Autonomous loop also continues after every normal completion until you turn it off or hit `loopMaxIterations`, so use it only when you want the agent to keep going on its own; Off disables all automatic messages for that session.

How do I confirm install or remove the plugin?

After restart, open **Plugins → dsh-client-auto-continue** and check **Running**, or dump config with `dsh --profile web --dump-config | grep -A 4 'id: auto-continue'`. To remove, run `dsh plugin --profile web remove dsh-client-auto-continue` and delete any stray `auto-continue` entry in `cordis.patch.yml` if needed.

08Data and sources

  • Author-claimedgithub.com1aff653f0e6a…

    It runs inside the DSH host, so it keeps working after you close the browser tab, and all tabs share one engine.

  • Author-claimedgithub.com1aff653f0e6a…

    DSH plugins install into a profile; `dsh web` uses the `web` profile. In the desktop app, install from its **Plugins** p…

This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-20. Found an error? Submit a correction.

🏆

Best DeepSeek Harness Plugins

Twelve plugins worth installing first — picked from the whole catalog, across every category.

DSH Plugins is an independent community directory of DeepSeek Harness plugins. Not affiliated with or endorsed by DeepSeek. Third-party plugins are not security-audited — review the source before installing.

New DeepSeek Harness plugins, weekly. No spam.