dsh-auto-continue

A DeepSeek Harness plugin that resumes interrupted sessions for you, with an optional autonomous loop.

English · 中文 · Русский · Changelog

Contents

• What it does
• Install
• Usage
• Configuration
• How it works
• Troubleshooting
• Privacy and permissions
• Development
• Links
• License

What it does

When a turn fails with a recoverable error, hits the output limit, ends without visible output, or is cut off by a host restart, the plugin waits a few seconds and sends a continue message for you. It runs inside the DSH host, so it keeps working after you close the browser tab, and all tabs share one engine.

• Error recovery. Network errors, timeouts, 5xx and 429 are retried with a grace period, a cooldown that grows after each failure, and a cap on consecutive attempts. Permanent errors (auth, balance, unknown model, context too long) are skipped.
• Offline hold. Network failures wait for the connection to come back instead of burning retries.
• Startup recovery. After a host restart, sessions interrupted in the last 15 minutes are resumed, including ones you have not reopened.
• Per-session modes. A switch next to the message box sets each conversation to Follow default, Off, Recovery only or Autonomous loop.
• Autonomous loop (opt-in). Keep a session going after normal completions, with an optional round limit.
• Safety. An idempotency guard tells the model whether the last tool call finished, and a loop guard stops turns that repeat themselves.
• Visibility. A settings page with today's statistics, recent recovery attempts and paused sessions, plus optional browser notifications with Resume now and Pause this session 1h buttons.

Install

DSH plugins install into a profile; dsh web uses the web profile. In the desktop app, install from its Plugins page instead of the CLI.

From npm (recommended)

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

Restart DSH and reload the browser after installing. Then open Plugins → dsh-client-auto-continue from the main sidebar to check that it is Running.

To update, let running work finish, stop DSH, run the same command again, then restart DSH and reload the browser. Your settings stay in the profile. The desktop app has its own profile: update it from the app's Plugins page.

Compatibility

DSH 0.1.0-rc.6 and earlier are not supported. Plugin 0.11.9 and 0.12.0 are rejected by DSH 0.2.0-rc.1's version check (#50). The desktop app's version is not the DSH runtime version; check the runtime (dsh --version for the CLI).

dsh plugin --profile web add github:HsiangNianian/dsh-auto-continue
dsh web

git clone https://github.com/HsiangNianian/dsh-auto-continue.git
cd dsh-auto-continue
npm ci
npm run build
dsh plugin --profile web add "link:$(pwd)"
dsh web

# the composed config should contain exactly one auto-continue entry
dsh --profile web --dump-config | grep -A 4 'id: auto-continue'

# uninstall
dsh plugin --profile web remove dsh-client-auto-continue

Usage

Recovery is on by default. Nothing else needs to be set up.

Session modes

The Auto-continue switch next to the message box applies to the current conversation only. The menu beside it picks a mode:

Turning the switch off selects Off; turning it on again selects Follow default. Choices are saved on the host right away (sessionModes), sync across tabs and survive restarts. Switching a conversation to Off cancels anything waiting to be sent but lets a running turn finish.

In a narrow window the label and menu collapse to an icon. DS-Bot and dsh-pocket get the same compact layout up to 640 CSS pixels. To hide the controls, turn off Show auto-continue switch in the composer in General and save; this does not change any session's mode.

Pausing and manual control

• Enable auto-continue globally (in General) is the master switch. Turning it off stops all automatic messages without forgetting per-session choices. The loop guard keeps running; turn off Loop guard too if you want no interruptions at all.
• Pause this session 1h (notification button) suspends one conversation for an hour.
• Resume now (notification button) sends one continue message immediately. It ignores cooldown, the consecutive limit and any pause, but does not lift the pause.
• Sending a message yourself, or a new turn starting, cancels any continue message that is still waiting.

Status and logs

The Status and logs category shows today's counts (continue messages, recoveries, failures, skipped errors, give-ups, loop breaks, by error code, with a reset button), the last 20 recovery attempts grouped by session, and the sessions that are currently paused. These live in host memory and reset when the plugin restarts. With Verbose logs on, every decision is logged with an [auto-continue] prefix in the DSH log (the terminal running dsh web for the CLI).

Configuration

Open Plugins → dsh-client-auto-continue from the main sidebar and pick a category. (Settings → Built-in plugins only lists component status; it is not the editor.) Edits are staged and take effect when you click Save; switching categories keeps your drafts, invalid values block the save, and Reset to default removes an override.

Settings are stored in the auto-continue entry of the active profile patch, ~/.dsh/profiles/web/cordis.patch.yml for the default web profile (older hosts: ~/.dsh/settings.yaml, under auto-continue:). You can edit the file directly; omitted keys use their defaults:

- id: auto-continue
  config:
    cooldownMs: 45000
    resumeCompletedTurns: true
    loopMaxIterations: 20

Times are in milliseconds. Text fields left empty use the built-in text in the current language.

General

Retry strategy

Startup recovery

Continue text

All default to '', which means the built-in text. Continue texts accept {code}, {message}, {status}, {tool}, {turn}, {errorCount} and {elapsed}; for example Continue ({tool}: {code}) becomes Continue (git push: UPSTREAM). Guard texts and the loop text accept {tool}, and guardDoneText also {result} (a short excerpt of the tool output).

Built-in texts exist in English, Chinese and Russian. They follow the DSH language: zh and zh-* use Chinese, ru and ru-* use Russian, every other locale uses English. Your own non-empty text is never replaced when the language changes.

Safety

Status and logs

Two keys are written by the plugin itself: locale (mirrors the DSH language, default en) and sessionModes (per-session choices from the composer, default {}). You normally do not edit them.

Error classification

With Classify errors on, network errors, timeouts, HTTP 5xx and 429 are retried. HTTP 401 and 403, and codes or messages about auth, credentials or API keys, balance or quota, unknown models, or context length are treated as permanent and skipped (with a notification if enabled). MALFORMED_RESPONSE is always retryable unless it carries an explicit 401 or 403.

If a provider returns an error that you know is safe to retry (check first that typing "continue" by hand works), add a narrow, stable fragment instead of turning classification off:

- id: auto-continue
  config:
    retryableErrorPatterns: |-
      Upstream rejected the request as invalid

Patterns are plain substrings, not regular expressions. Cooldown and Max consecutive still apply.

How it works

1. Triggers. The engine listens to session events in the host. A turn/end with error, max-tokens, a silent ending, or completed (loop mode only) starts the flow. After a host restart, the startup scan checks open and stored sessions every 3 seconds until the scan window ends. The loop guard watches running turns and cancels one that repeats itself.
2. Session check. Nothing is sent while auto-continue is paused globally, the session is Off or paused for an hour, or the session is a subagent and Resume subagent sessions is off. A subagent follows its main conversation's mode unless it has its own, and never runs the autonomous loop or the loop guard.
3. End reason. Manual Stop and policy blocks (blocked) are left alone, and so are permanent errors. Everything else recoverable goes to recovery. A normal completion only continues in Autonomous loop mode, which skips the cooldown and the consecutive limit but respects loopMaxIterations.
4. Retry budget. Recovery stops at Max consecutive. Inside the cooldown, the send is deferred rather than dropped. The cooldown is multiplied by the backoff factor after each failure, up to the maximum.
5. Grace period. The engine waits graceMs. A new turn or a message from you cancels the send.
6. Offline hold. For network errors, the host checks for a non-loopback network interface and one resolvable public name. While offline it waits and re-checks every offlineCheckMs, then goes through grace and cooldown again. With HTTP(S)_PROXY or ALL_PROXY set, only interfaces are checked.
7. Send. The engine picks the text for the reason, appends the idempotency-guard note, and sends it with agent.followup using the session's preset and model. If user turns are already queued, the continue message is moved ahead of them while their order is kept. With resumeGoals on, a goal the restart disarmed is re-armed.

Child sessions. Outside of Resume subagent sessions, subagent and team-member sessions are never resumed directly, and that setting only covers live ones. After a restart, with Wake child sessions after restart on, the startup scan collects children a restart interrupted (at most 8 child logs per pass) and sends their root session one message listing them, once per batch. The root decides whether to continue or wrap up. A root still mid-turn is left to normal recovery, and a root you stopped yourself is never woken.

Unreadable sessions. If a session's history cannot be read during the startup scan, that session is skipped and an error is logged; other sessions still recover (#58). Repair it and restart DSH within the scan window to try again.

Troubleshooting

Privacy and permissions

• The engine runs in the DSH host and reads session events and history through DSH services. No third-party service is contacted and no credentials are stored.
• Continue messages go through agent.followup; the loop guard may call agent.cancel first. A resumed agent keeps the session's existing tools and permissions.
• The offline check reads the local network interfaces and does a DNS lookup of api.deepseek.com, www.baidu.com and one.one.one.one. It opens no connection and sends no request.
• Settings are saved through DSH's settings API to the active profile (or ~/.dsh/settings.yaml on older hosts). Retry counters, cooldowns, one-hour pauses and statistics are kept in memory only.
• Browser notifications are opt-in. Permission is requested only when you turn them on and save.

Development

Use Node.js 22.

npm ci
npm run typecheck
npm run build
npm test

npm run test:runtime runs the settings, startup-recovery and restart tests against published DSH packages. Install the pinned fixtures first:

for v in 0.1.7 0.2.0 0.2.0-rc.2 0.2.1 0.2.1-rc.2; do npm ci --prefix "tests/fixtures/dsh-$v"; done
npm run test:runtime

The runtime tests drive real DSH services with a deterministic model adapter; they make no requests to a model provider. CI also checks that the committed lib/ matches a fresh build and runs dsh-plugin-check.

The banners and social preview are generated by npm run docs:assets; the workflow map is an Archify export (docs/auto-continue-workflow.*, sources in *.archify.json) (render the PNG with rsvg-convert -w 1280 -h 640 docs/social-preview.svg -o docs/social-preview.png). See docs/screenshots/README.md for how the screenshots are captured.

Links

• Repository: github.com/HsiangNianian/dsh-auto-continue
• npm: dsh-client-auto-continue
• DeepSeek Harness: github.com/deepseek-ai/deepseek-harness
• dsh-plugin-check: github.com/omdsh-dev/dsh-plugin-check
• LINUX DO: linux.do

License

MIT © Hsiang Nianian