dsh-task-runner

The DSH sidebar is organized around workspaces, and every session is tethered to a folder. When you just want a quick ephemeral task that needs no workspace context, it ends up buried in the Ungrouped bucket; EAC desktop on top of that ships its own temporary-session plugin, so two overlapping mechanisms coexist and the mental model gets muddled. dsh-task-runner upgrades the sidebar into a flat Project / Task dual-group layout. The Project group keeps its existing behavior untouched, while the Task group becomes a first-class home for every workspace-free session (including legacy Ungrouped entries), with a friendly placeholder when empty and a "+" button right in the heading that creates and switches to a new task instantly, auto-named, no dialog.

Each task is provisioned in an isolated temporary directory (default D:\dsh_working-) and opened as a ready-to-use session, fully decoupled from the workspace registry. A dedicated task panel at the bottom of the sidebar lets you reopen existing tasks, clean up a single one, or batch-clear all finished and missing tasks. The /task command inside any session offers the same operations. Under the hood the plugin relies entirely on the official session.create({ cwd }) API with host-side hooks for automatic registration and recycling, so no core hacks are needed. A companion patch script auto-detects the EAC 4.1 versus 4.2 sidebar layout, applies idempotent rendering patches, and can be re-run after any EAC upgrade to fully restore the task UI.

Best suited for everyday DSH and DSH EAC users who frequently kick off one-shot prompts, snippet rewrites, quick translations, or ad-hoc queries that need no workspace context, and for teams who find the Ungrouped bucket messy and want a single, clear entry point for ephemeral work. Safety boundaries are thorough: path-traversal guards keep all directory operations inside the task root, the root itself is never treated as a task for cleanup, active tasks require an explicit force flag before deletion, and sub-agent sessions are excluded from task registration, so your data stays safe by default.