AI Agent Hub
Back to plugins
🖥️

dsh-desktop

Client Updated 2026.08.16

Run the following command in DeepSeek Harness:

dsh plugin install ahikl/dsh-desktop

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

In DeepSeek Harness, run dsh plugin install ahikl/dsh-desktop to install this desktop plugin; source at https://github.com/ahikl/dsh-desktop.

About this plugin

The dsh Web UI was designed for a browser tab, which means every session starts with opening a tab and typing a URL. That small friction adds up over weeks of daily use. dsh-desktop closes the gap by wrapping the Web UI in a frameless Electron window with a dsh-styled custom title bar that follows the active theme, so the interface feels like a native desktop application rather than yet another tab.

On the desktop-interaction side it adds a tight feature set: a system tray menu for showing the main window, opening in a browser, or quitting entirely; closing the window minimizes to the tray instead of shutting down. URL resolution follows a clear priority chain (command-line flag, then an already-running Web Server port, then auto-starting dsh web), so even if you have never manually launched a browser service, the plugin boots the Web UI as a child process and then launches Electron on top of it, with no manual parameter stitching required.

It is well suited for developers who rely on dsh every day and want to cut down on switching between browser tabs and the terminal. As a fully out-of-tree plugin, dsh-desktop injects nothing into the dsh source tree and does not add Electron to the dependency graph; removing it cleanly reverts you to the pure Web workflow with zero residue.

Use Cases

  • Frequent dsh users who want to skip the repeated browser-tab ritual
  • Users who prefer a frameless window with a custom title bar for a native-app feel
  • Quickly invoke, minimize, or quit the dsh desktop window from the system tray

Best For

  • Engineers who rely on dsh daily for development or debugging
  • Users who favour a desktop-first workflow and want fewer browser-terminal context switches
  • Team leads who want a consistent dsh look across machines without touching core source code