gorban/dsh-job-stop

Makes the session header's background-job list actionable: hover a running row, click the stop sign, confirm against the full command.

Turns a read-only projection into a human control. ctx.jobs already ran every background bash, pwsh, PTY and subagent job, and dsh-tool-jobs already exposed job_kill — to the model. The web list (dsh-client-ui-jobs) was deliberately read-only, so a human watching a runaway job in the session header had no way to stop it. Here, hovering a running row covers its animated state dot with a red stop button; confirming opens a dialog that restates the command, kind, status, elapsed time and job id before anything is cancelled, and for bash that command is untruncated, which is the whole reason the dialog is worth reading. On confirm the host kills the job through ctx.jobs, the row flips to stopping and then killed from the ordinary pushed frame, and the owning agent is told that a human stopped its job. The record of that kill is a fixed English string, stopped by the user from the background-job list, kept stable so it greps in logs and in a job's terminal detail. The limits are stated: only running rows offer the affordance, a session with no live agent cannot have its jobs stopped (409, because the kill is fenced by that exact owner instance), and stopping a job does not remove its run_in_background card from the transcript.

Web UI Enhancements ★ 1
View on GitHub ↗

Install

dsh plugin --profile web add @gorban/dsh-job-stop

The npm line from the README's Install section, and it is prebuilt, so the install needs no build step and no allowBuilds approval. A GitHub form (dsh plugin --profile web add github:gorban/dsh-job-stop) and a release-tarball form (dsh plugin --profile web add https://github.com/gorban/dsh-job-stop/releases/latest/download/dsh-job-stop.tgz) are documented as well. Dependencies are deliberately not declared as peer dependencies — the README explains that declaring them makes a standalone pnpm install try to fetch harness packages from npm, and at least one published range resolves to a build whose tree depends on @deepseek-ai/dsh-type-meta, which is not published.

Compatibility

Requires dsh 0.1.2-alpha.1 or newer, declared as engines.dsh so the Plugin Market's host-aware filter can read it; both the jobsBySession mirror this list renders from and the ctx.connection.fetch route seam the stop endpoint is claimed on first shipped in that release. Every dependency is provided by the dsh installation it runs inside and resolved from the host's module graph, so the plugin pins itself to no harness build. The shipped @deepseek-ai/dsh-client-ui-jobs row can stay enabled: this plugin registers its list under that entry's own slot cell id (job-list) at a lower priority, so the header keeps exactly one control and the read-only list is shadowed rather than duplicated. That shadow is the main coupling risk, and the README names it — if upstream renames the job-list slot entry, both lists would render, and the fix is a one-line id change.

Details

Alternatives

liguobao/dsh-desktop · mrbeandev/dsh-desktop-ui · longyu065/dsh-desktop

More plugins in Web UI Enhancements

Browse more in Web UI Enhancements

Guides for Web UI Enhancements plugins