DeepSeek Harness plugin · v1.1.0

dsh-auto-workflow

Persistent, concurrent workflows for DeepSeek Harness.

Agents, commands, HTTP calls and Human decisions in one durable graph. The plugin core is a generic runtime; the PR-native development flow is one replaceable example, not the product definition.

持久化、并发的通用节点图运行时;自动开发流只是示例,不是功能边界。

Key ideas

three things to know

Generic runtime

Graphs, node types, artifacts, permissions and the board are the core. No specific development process is built into the plugin.

Persistent and concurrent

New packets arrive anytime. Human waits and slow tasks do not stop unrelated work.

Examples, not the product

The 3-engineer/PR workflow is bundled application code. Replace it with your own graph, roles and merge policy.

Read the full overview in the repository →

Example: requirement lifecycle

bundled example · not core
Lifecycle diagram: requirement, branch and worktree, draft PR, review and brief, ready PR, external merge or Human-approved self-merge, verify and cleanup.
This is the bundled development example: one requirement, one branch/worktree, one PR. External reviewers can merge directly; after a grace period, Human approval can authorize a workflow self-merge. The plugin core does not require Git, PRs or GitHub.

Development workflow, branch rules and merge policy →

Architecture

core runtime · one engine
Architecture diagram: the dsh-auto-workflow engine runs in the DSH Host with scheduler, packet state, artifacts and permissions; it drives agent, command, HTTP and Human executors and exposes a private board.
The core engine owns scheduling, state, artifacts and permission checks. Executors only do the work; the private board is where Humans see details and decide.

Plugin model, nodes and protocol reference →

Get started

v1.1.0

Install the plugin, then open a workflow from a DSH session. The development flow is an example you can adapt.

dsh plugin --profile desktop add \
  github:lyingloong/dsh-auto-workflow#v1.1.0

README · Workflow guarantees · Releases