DeepSeek Harness Plugin Hub

Publish and manage complete Harness Profiles. Discover Plugins for your next setup.

Explore

PluginsPresetsDocsNews

Community

Publish a pluginContactReport an issue

Resources

Plugin Hub on GitHubDeepSeek HarnessSystem statusPrivacy notice
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

Independent and unofficial. Not affiliated with, authorized by, or endorsed by DeepSeek.

Quick Restart — DSH Plugin for DeepSeek Harness
← Plugins
Q

dsh-quick-restart

Quick Restart

One-click restart for the DeepSeek Harness Web UI: safely restart the whole dsh web process (supervised external helper, task-aware graceful stop, auto-reconnect). / DSH Web 界面一键安全重启:重启整个 dsh web 进程,让新装、更新或改配置的插件立即生效。

The plugin will be installed here. Keep web if you are unsure.

npx -y @deepseek-ai/dsh plugin --profile web add github:zhuifengqug/dsh-quick-restart#800448103d15fb59c263d9bfaacb9de4f9b915b7
READMECompatibilityVersions

Compatibility and provenance

Quick Restart is published as dsh-quick-restart and currently resolves to version 0.3.0. The Hub verifies its manifest and preserves the exact installation source for reproducible installs.

DSH compatibility
*
Runtime surfaces
web
Release source
github
Registry updated
9/17/2026

Versions

0.3.0
stable
9/17/2026
0.2.1stable
8/22/2026
0.2.0stable
8/21/2026

Related plugins

Loading related plugins…

Latest
0.3.0
DSH
*
HMR
Process restart
Tree shaking
Safe tree shaking not declared
Unpacked size
Unavailable
Files
Unavailable
Surface
web
License
MIT
Source
github
GitHub
★ 0
Weekly downloads
0
Last push
9/17/2026
View source ↗
README badge

Click the badge to copy Markdown for your README.

Do you maintain this Plugin?Claim benefit · Priority security scan

Verify the GitHub repository declared in package.json to manage this listing. After you claim it, Hub will prioritize a security scan of the current version and publish the result when it passes.

Claim this Plugin →
Report an issue
DeepSeek Harness Plugin Hub
ProfilesPluginsCategoriesNewsDocsSign inManage Profiles
ProfilesPluginsCategoriesNewsDocsSign in

Related plugins

More verified plugins in productivity-workflow.

Acp App@deepseek-ai/dsh-acp-appThe dsh ACP profile bundle: automation-only JSON-RPC stdio and process lifecycle over dsh-baseClient Ui Task Board@linxin666/dsh-client-ui-task-boardHost-authoritative task board for the DSH Web GUI with real session execution, Host cron scheduling, and optional cross-platform idle-sleep protection; mounted without DSH source changes.Web All@linxin666/dsh-web-allDSH Web UI 全家桶聚合插件:一键安装全部功能插件(task-board / git-graph / pet / remote-web-ui / web-ui-settings / skin-center / community-plugins / compat shim)。compat 桥接层已并入本包(src/client),无需独立 compat npm 包。Deepseek Ipptdeepseek-ipptiPolloWork PPT Studio and its curated slide templates as a native DeepSeek Harness conversation view.

README

dsh-quick-restart

One-click restart for the DeepSeek Harness Web UI — restarts the whole dsh web process so freshly installed, updated, or reconfigured plugins and settings take effect immediately. The Edge/PWA window stays open and reconnects on its own.

中文说明见 README.zh.md。

Why it needs an external helper

DSH has no official "restart the process" API. The only official way to stop it is the graceful path behind ctx.appExit() (dispose the root fiber tree, close the listening socket, let Node exit normally — never process.exit(), which can trip a libuv assertion on Windows).

Restarting itself is the hard part: when DSH runs under a supervisor (e.g. Start-DSH-GUI.ps1), that supervisor puts the process into a Windows Job Object with JOB_OBJECT_LIMIT_KILL_ON_JOB_CLOSE. Everything inside that job — including plain spawn({ detached: true }) children — dies with it. So the thing that brings DSH back must live outside the job:

  • the helper is created through WMI Win32_Process.Create (its parent becomes WmiPrvSE.exe, so it escapes the job),
  • the plugin verifies that parent before touching DSH: if the helper cannot be confirmed alive outside the job, the restart is aborted and DSH is left untouched.

What you get

  • Sidebar entry (sidebar.footer.action, next to Settings) plus a full page under Settings → Quick Restart.
  • Explicit state machine: idle → checking → waiting-for-tasks → (confirming-force-restart) → preparing-helper → stopping → starting → waiting-for-ready → succeeded | failed.
  • Task-aware: waits for running agents / background jobs / subagents / workflows instead of killing them; on timeout it asks you before a force restart, and only then cancels work.
  • Nothing dies silently: helper launch failure, port-not-released, or service-not-ready all abort with a readable reason in the panel and in the state file.
  • Multi-instance safe: state, lock and log files are keyed by port-pid; process kills are verified by PID + creation time + port ownership (never "kill every node.exe").
  • Result survives a page reload: a new instance recognises its own birth record (newInstance.pid === self) and reports "this instance was started by Quick Restart".

Install

The plugin installs as a profile bundle (the dsh.bundle.patch entry adds it to the profile's cordis.patch.yml):

// <DSH_HOME>/profiles/web/package.json
"dependencies": { "dsh-quick-restart": "link:D:/path/to/dsh-quick-restart" }
# <DSH_HOME>/profiles/web/cordis.patch.yml
- insert:
    - id: dsh-quick-restart
      name: dsh-quick-restart

Then restart DSH once manually (that is the bootstrapping problem this plugin solves afterwards). A page reload is enough for client-half changes — DSH re-hashes plugin bundles and serves the new revision.

Configuration

FieldDefaultMeaning
enabledtrueShow/enable the entry
gracefulShutdownTimeoutMs30000How long to wait for running tasks (1000–3600000)
startupTimeoutMs60000How long to wait for the service to come back (5000–1800000)
reconnectEnabledtrueRead the real result back after reconnecting
requireConfirmationWhenBusytrueAsk before restarting while tasks run

Values are clamped/validated; unlimited waits are rejected on purpose.

Development

npm run typecheck    # tsc --noEmit
npm run build        # type stripping + copy client bundle & helper into lib/
npm test             # 20 unit tests (state machine, locks, recipes, redaction, birth record)
npm run test:launch  # helper launch regression (fake new instance, no real DSH)
npm run e2e          # full restart against a throwaway instance

src/ is the single source of truth; lib/ is a committed build artifact (DSH loads lib/index.js, and git installs must work without a build step).

Limitations (by design)

  1. DSH has no global drain gate, so new work can still arrive while waiting for tasks.
  2. ctx.workflowEngine has no list() — workflows are only observable through events.
  3. Environment variables whose names look like credentials are not forwarded across the restart (only their names are reported).
  4. Credential-like values must live in $DSH_HOME/.credentials.yaml, not in the environment.
  5. Windows-only (Job Object / WMI / Get-NetTCPConnection semantics).

License

MIT