dsh-bgjobs

Submitting a command in DSH that takes dozens of minutes carries an obvious risk: if the DSH process closes or crashes, the task dies with it. bgjobs eliminates that coupling by handing off to the Windows Task Scheduler service. Once dispatched, the task runs fully independent of DSH — close the app, close the browser, even crash DSH, and the job keeps going.

The main experience revolves around a floating real-time output panel in the bottom-right of the DSH web UI: stdout refreshes every second, and the panel is draggable, minimizable to a floating ball, groupable by workspace, and theme-aware. When a job exits, a toast notification appears without interrupting the current conversation; optionally, the result can be routed back to the originating agent via a notify parameter. After a DSH restart, tracking resumes automatically for in-flight and historical jobs. When DSH is not running at all, a standalone CLI and a desktop GUI both provide submit, log, kill, and cleanup operations. PowerShell jobs can additionally accept a sandbox flag to constrain file-write permissions.

Built for users who routinely kick off long-running tasks in DSH — large downloads, batch scripts, builds, data sync or export — and want to fire and forget rather than babysit a terminal.