Introduction¶
DeepSeek Harness (DSH) provides a Web-based agent development environment. During use, developers often need to keep the Web UI running for extended periods. The traditional approach of directly opening a browser has several issues: closing the window interrupts the service, multiple instances cannot be easily distinguished, and there is no system tray management. dsh-web-manager addresses these problems by providing a Windows tray application, WSL companion scripts, and a runtime bridge.
What Is It¶
dsh-web-manager is a management tool for the DeepSeek Harness WebUI. It includes Windows system tray management, WSL companion scripts, and a DSH internal runtime bridge. It is distributed as a dsh plugin package and can be easily integrated into a DSH Profile.
- Maintainer: FYHC1
- Category: Client
- License: MIT
Core Features¶
- Persistent Windows system tray management
- WSL companion scripts and backend hosting
- DSH runtime bridge (v3.0)
- Edge / Chrome / Chromium application window management
- Automatic creation and maintenance of desktop shortcuts
- Automatic update mechanism
- Multi-instance support
Installation and Enabling¶
The plugin exists as a plugin package. After installation, the tray application and shortcuts are automatically deployed when DSH starts.
- Add the plugin to a DSH Profile using the following command:
dsh plugin --profile web add github:FYHC1/dsh-web-manager
- After installation is complete, restart the DSH process to activate the tray application and shortcuts.
Typical Usage¶
After installation, you can use it in the following ways:
- Command-line startup:
dsh-web-manager.exe open windows
dsh-web-manager.exe open wsl
dsh-web-manager.exe "backend wsl"
- WSL command line:
wslmode systemd
- Shortcuts:
After installation, desktop shortcutsDeepSeek Harness WebUI (win).lnkor(wsl).lnkare automatically generated. Double-click to open.
Notes¶
- Background daemon: Closing the browser window does not terminate the dsh web background service; the tray application continues to run in the background.
- Window size: Window size is set via WinEventHook before the window is displayed to ensure accurate size memory.
- Browser selection: Edge is used by default; if it is not installed, it automatically falls back to Chrome or Chromium.
- WSL Systemd: Using the WSL systemd hosting mode requires
[boot] systemd=trueto be enabled in the WSL configuration file/etc/wsl.conf. - Runtime Bridge port: The Runtime Bridge listens on
127.0.0.1:<webPort+100>.
Conclusion¶
dsh-web-manager transforms browser windows into a native application experience using the --app mode of Edge/Chrome. Combined with tray management, it solves the pain points of long-running DSH WebUI usage and window management. It supports multiple instances and multiple backends, and can automatically maintain shortcuts, making it suitable for scenarios where the Web UI must remain resident for extended agent development.