Skip to content

icetomoyo/dsh_workflow

600Last commit Aug 13, 2026

dsh_workflow DSH plugin

DSH Workflow adds a product-level workflow layer on top of DeepSeek Harness, enabling naming, discovery, reuse, pause/resume, rerun, and persistent evidence. It provides a complete KodaX-inspired execution model with versioned capsules, run graphs, and safety boundaries.

How to install the dsh_workflow DSH plugin

dsh plugin --profile web add "github:dsh-external/dsh_workflow#main

Copying does not run this command. Review the repository and version before installing the dsh_workflow DSH plugin.

dsh_workflow DSH plugin data source

dsh_workflow DSH plugin snapshot date: Aug 16, 2026

discovered

What the dsh_workflow DSH plugin can do

  • Versioned capsule manifest with intent, inputs, requirements, and provenance
  • Full WorkflowApi: phase, spawnAgent, runAgent, parallel, pipeline, synthesize, artifact, log, budget
  • Deterministic discovery: built-in, project `.dsh/workflows`, personal `$DSH_HOME/workflows`
  • Durable run persistence with immutable snapshots, event logs, and effect cache for resume
  • Safety: capability-only VM for generated scripts, trust boundaries, read-only allowlists, approval modes

Where the dsh_workflow DSH plugin fits

  • Create reusable parallel investigation workflows for recurring code reviews
  • Save and rerun complex multi-agent pipelines with versioned manifests
  • Pause a long-running workflow and resume later with cache hits on completed tasks
  • Govern cost and token usage with per-run budgets and hard limits
  • Share workflow capsules across team members for consistent agent orchestration

Who the dsh_workflow DSH plugin is for

  • DSH users who need to formalize multi-agent workflows beyond ad-hoc sessions
  • Teams managing agentic processes that require auditability, cost tracking, and reproducibility

dsh_workflow DSH plugin limitations

  • Trusted-local `.ts` workflows use Node 22 native erasable-syntax TypeScript and require restart for cache refresh
  • Current DSH subagent seam lacks native support for existing-agent target, per-agent effort, and worktree – adapters must be registered or fail loud
  • Verification of non-Git workspaces or external authority requires custom verification adapters
  • Only generated capsules preserve immutable script snapshots; pure function trusted-package runs cannot be saved from run ID

dsh_workflow DSH plugin: from the repository README

Quoted from the icetomoyo/dsh_workflow README, the upstream source of the dsh_workflow DSH plugin. Copyright remains with the original authors.

中文 · <a href="README.en.md">English</a> · <a href="#快速开始">快速开始</a> · <a href="#它为-dsh-带来什么">DSH 价值</a> · <a href="#能力">能力</a> · <a href="docs/KODAX_PARITY.md">对标矩阵</a> </p> `@dsh-external/workflow` 是一个官方 bundle 形态、零核心 patch 的 DSH 插件。它完整参考 KodaX 的 workflow 设计能力,并针对 DSH 的 Cordis、`ctx.subagents`、Session、后台 jobs、审批、命令和工具机制做独立实现。 它不替换 DSH 已有的前台 `workflow` 工具。原生工具适合“这一次把若干工作并行跑完”;本插件负责更高一层的流程产品能力:命名、发现、生成、复用、暂停/恢复、重跑/续跑、持久证据、成本记录和治理。 ## 它为 DSH 带来什么 DSH 已经有很强的 Harness 基础设施:模型路由、子 Agent provider、工具权限、审批、Session 日志、后台 jobs 与 UI 事件。但仅有这些“执行原语”,团队仍需在每次会话里重新描述如何拆解、并发、验证和汇总。 | 只有一次性调度时 | 安装 DSH Workflow 后 | | --- | --- | | 每轮重新提示如何拆任务,策略难复用 | 保存为项目或个人 workflow,按名字运行 | | 并行结果散落在会话里 | run graph、事件、artifact、结果摘要和成本永久落盘 | | 中断后通常从头重来 | 按 run snapshot 重跑,或用 effect cache 续跑未完成部分 | | provider/模型/并发/预算靠提示词约束 | manifest + preflight + 运行时硬限制 | | 生成的脚本容易越权或不可复现 | capability-only VM、JSON 边界、确定性 guard、审批分级 | | 复杂流程只有作者自己知道怎么用 | capsule 自带 intent、inputs、requirements、provenance | | 多 Agent 是一次性技巧 | 多 Agent 变成可审计、可分享、可演进的工程资产 | 对 DSH 项目本身,这个插件的价值是把已有 Harness 能力串成完整闭环: ```mermaid flowchart LR A["DSH providers / models"] --> W["DSH Workflow"] B["tool filters / approval"] --> W C["Session / j

Read the full READMERepository license: MIT

dsh_workflow DSH plugin questions

How do I install DSH Workflow plugin?

Run the command `dsh plugin --profile web add "github:dsh-external/dsh_workflow#main"` in your terminal. This requires Node.js >=22.19 and a compatible DSH snapshot. After adding, restart your DSH profile and verify the bundle appears in the config dump.

Can I reuse a workflow I created in a previous session?

Yes. You can save any generated workflow capsule using `/workflow save <runId> <name> [project|personal]`. The workflow is stored in `.dsh/workflows` (project) or `$DSH_HOME/workflows` (personal) and can be run later by name via `/workflow <name> [JSON args]`.

What happens if a workflow is interrupted before finishing?

The run state is persisted with a `running` or `paused` status. You can later use `/workflow resume-run <runId>` to continue from where it left off. Completed tasks with valid effect cache are skipped; only unfinished tasks are re-executed.

How does the plugin handle security for generated scripts?

Generated scripts run in a QuickJS WebAssembly sandbox with no access to host APIs. They can only interact through a frozen JSON capability RPC. Static policy blocks import/require, process, file, shell, network, timer, and non-deterministic APIs. Trusted-local workflows run with full Node privileges but require explicit approval.

Can I use this plugin with other DSH clients besides the web UI?

Yes. The plugin works with any DSH client that supports the plugin system, including CLI and other frontends. The workflow commands are available via slash commands and model tools. However, the web UI's left workspace has special handling for session management as described in the README.