v0.1.2

Fixes three ways this plugin could be less careful than dsh-tool-jobs about the notice it delivers to the agent, plus one readability gap.

A job that finished while you were confirming is no longer announced by nobody. The handler reads the job and then kills it; if the job reached a terminal state inside that window, kill() claims the record's reported flag — the same flag dsh-tool-jobs suppresses its own completion notice with — so nothing told the agent the job had ended. That path now reports the settled outcome itself. A job that was merely already stopping stays silent, because whoever asked for that stop already knows.

Notices respect a producer's model-facing cap. dsh-tool-jobs bounds its completion notice to outputLimitBytes; this plugin bounded nothing, which mattered only for PTY sends, whose label is caller text with no length of its own. The notice is now clipped to that cap, dropping only the label and keeping the job id and the job_output pointer.

Delivery is bounded by a wake budget. New maxConsecutiveWakes (default 3, mirroring dsh-tool-jobs) caps how many turns this plugin may open on one agent between that agent's own human inputs. Past the budget the account is still delivered — injected rather than waking the agent — so a burst of stops cannot spend a model request each.

The agent is told how long the job had been running (after 5m 3s), which the dialog already showed the human.

The README now opens with a short demo GIF of the hover-to-stop interaction.

Requires dsh >= 0.1.2-alpha.1.

v0.1.1

Packaging-only release; the plugin behaves identically to 0.1.0.

• Drops the project .npmrc, whose pnpm-only keys made every npm command print a deprecation warning. Nothing depended on them.
• Releases now publish to npm from GitHub Actions with a provenance attestation, so the registry records that the tarball was built from tag v0.1.1 rather than uploaded by hand.

v0.1.0

First release. Hover a running row in the session-header background-job list and its animated state dot is covered by a stop button; activating it opens a confirmation dialog that restates the full command, kind, status, elapsed time, and job id before anything is cancelled.

Requires dsh >= 0.1.2-alpha.1.

• Adds the human stop path for ctx.jobs work — background bash, pwsh, PTY sends, and one-shot background subagents — which previously only the model's job_kill tool could reach.
• The stop endpoint is claimed on the Connection fetch registry, so it sits behind the host/Origin trust and browser-authentication fence rather than ahead of it.
• A successful stop delivers a plugin-sourced notice to the owning agent, because kill() marks the job reported and dsh-tool-jobs suppresses its own completion notice for a reported job.
• A job that already left running is never killed, so the completion notice the model is still owed survives.
• English and Simplified Chinese copy, keyboard reachable, prefers-reduced-motion respected.