AI Agent Hub
Back to plugins
🖥️

dsh-restart-btn

Client Updated 2026.09.16

Run the following command in DeepSeek Harness:

dsh plugin install SiriusWJ/dsh-restart-btn

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

Run dsh plugin install SiriusWJ/dsh-restart-btn in DeepSeek Harness to install; source code is available at https://github.com/SiriusWJ/dsh-restart-btn

About this plugin

After tweaking a plugin, theme, or config, dsh web needs a restart to pick up the changes. The old workflow meant double-clicking a desktop shortcut or typing commands in a terminal by hand. Once you switch machines or launch method, things fail silently: PowerShell is blocked, paths contain non-ASCII characters, another process squats on the port. These lookalike-success failures are maddening to debug.

dsh-restart-btn adds a single button to the General section of the DSH settings page. One click delegates the work to a helper process spawned by the very node instance currently serving your session. The helper locates the old process by listening port, terminates it, and relaunches the service with the original argv, execArgv, and working directory. No PowerShell, no scheduled tasks, no elevation required. When the new service is up, the page reloads itself and the auth cookie refreshes automatically, so open tabs never get flushed into a wall of 401s. Windows (with or without a console, under AppLocker, with space-laden paths), Linux, macOS, WSL, nvm / volta / pnpm global installs, and non-default ports are all handled explicitly; failures return a stable error code rather than a silent false success.

Built for people who fiddle with plugins, themes, or config daily and refuse to maintain a different restart ritual per machine. One button replaces every manual step and works the same way regardless of where you are.

Use Cases

  • Restart dsh web with one click after changing a plugin, theme, or config setting
  • Switched to a new machine or WSL / service launch mode without re-authoring restart scripts
  • PowerShell is blocked by AppLocker or execution policy while you still need to restart the web service

Best For

  • DSH users who tweak plugins and themes often and want to skip terminal commands
  • Developers maintaining dsh across multiple machines and launch methods
  • Users on restricted Windows systems where PowerShell is unavailable yet dsh web still needs restarting