Introduction

DeepSeek Harness (DSH) supports extending capabilities through plugins. dsh-workflows is an installable bundle for managing saved JavaScript workflow definitions, supervised background execution, durable checkpoints, slash commands, and a Web dashboard. It complements the base Harness capabilities, enabling developers to persist workflow scripts and execute and monitor them in the background.

Core Features

The plugin provides the following core capabilities:
* Saved workflows: Supports saving JavaScript workflow definitions as files, including metadata and the script body.
* Background execution and supervision: Supports starting workflows in the background, with runtime supervision and monitoring.
* Durable checkpoints: Preserves execution checkpoints and logs for later review.
* Web dashboard: Provides a visual Web interface to manage definitions and view execution status.
* Slash commands: Provides command-line shortcuts such as /create-workflow, /workflows, and /workflow.
* Compatibility assessment: Includes an MIT-licensed compatibility assessor for safe replays.

Environment Requirements and Installation

Before installing, confirm the runtime environment.

Prerequisites:
* Node.js version must satisfy ^22.19.0 || >=24.0.0.
* Must use pnpm@11.7.0.

Installation steps:
1. Ensure pnpm is included in the PATH of the service user.
2. Run the installation command. This command adds a dependency and a bundle layer; no manual build is required.

dsh plugin --profile web add @zaalipro/dsh-workflows@0.1.0-rc.5
dsh plugin --profile headless add @zaalipro/dsh-workflows@0.1.0-rc.5

Compatibility note:
This plugin is compiled and tested against the official DeepSeek Harness 0.1.2-rc.1. Stock Harness 0.1.0-rc.8 and later unreleased versions are currently not supported.

Typical Usage

After installation, you can operate via slash commands.

Create a workflow:
Use /create-workflow [detail] to create one. This command collects intent, generates JavaScript code, performs one simulated validation, and then saves the result. Metadata is stored as JSON data, and the script is pure JavaScript.

Start a workflow:
Use /workflow <name> [<json-args>] or its generated alias to start a saved definition.
* /workflow review-changes: Starts the definition named review-changes directly.
* /workflow review-changes {"arg": "val"}: Starts with arguments.
* After the command returns, the workflow starts in the background; use /workflows to monitor it.

View the dashboard:
* In Web mode, use /workflows to open the Web dashboard and view all saved definitions, live execution status, stage details, logs, and terminal results.
* Use /workflow without arguments to open the selector for saved definitions.

Runtime Behavior and Limitations

Understanding the runtime behavior helps handle abnormal cases correctly.

Runtime storage:
Workflow definitions are usually located in one of the following places:
1. The configured bundled root.
2. The .dsh/workflows directory of a Git project (or the Session cwd).
3. $DSH_HOME/workflows.

Execution data is stored under the $DSH_HOME/workflow-runs directory.

Recovery and interruption:
* Pause and resume: Pause and resume are supported only within the same process.
* Process death: If a process dies unexpectedly, active execution records are converted to an unrecoverable Interrupted status. In this case, Resume or Save is not available; only checkpoint data is preserved.
* Replay mechanism: Only checkpoints reached after the assessor enters a quiescent state have replay authority. External side effects (such as non-committed calls) will be executed again during replay, so idempotency is important.

Parameters and scope:
* User scope (save_scope: "user") works without requiring the Session cwd.
* Structured agent() parameters must conform to a specific format (minItems/maxItems must be non-negative integers, and they must not be mixed with oneOf).

Ecosystem and Resources

This plugin is maintained by zaalipro and follows the MIT license.