dsh-plugin-autoqueue

Anyone who has pushed a batch of Markdown prompts through DSH probably knows the drill: paste the prompt into the foreground chat, watch it run, manually resume when it hits a block, retry on timeout, then clean up the output yourself. Once the queue grows, foreground conversation and background dispatch start fighting for the same session. autoqueue solves this with a deliberately narrow scope — an unattended task queue that dispatches, unblocks, retries, settles, and archives tasks on its own, while your foreground DSH sessions keep chatting exactly as if nothing changed.

The isolation model is session-granular. Every task binds to a dedicated session and its own working directory, with approvalPolicy pinned to never and execution restricted to two versioned engine presets that forbid questions, detached processes, and any escape from the owned session. When a foreground session is active, a running goal goes through a persistent pause-before-cancel hand-off and only resumes after two consecutive trusted idle observations — no duplicate prompt injection. On the outside, the plugin exposes 16 autoqueue_* Host tools, a full HTTP API with an OpenAPI 3.1 description, and a compact SSE event stream. The built-in React dashboard in the DSH sidebar covers the entire lifecycle from creation and editing to stopping, archiving, and restoring. Scheduling supports one-shot ISO 8601 timestamps, five-field cron recurrence, wall-clock deadlines, and per-attempt timeouts across a six-state machine.

autoqueue is the missing queue layer if you have structured Markdown tasks that need to run on a schedule, in a loop, or on demand from an external AI, CI pipeline, or script — without ever touching the foreground. It does not replace DSH; it simply gives DSH a pair of hands for the background.