DeepSeek Harness (DSH) uses a plugin-based architecture, but merely listing plugins is often insufficient to reproduce an environment. Differences in plugin loading order, version drift, and configuration patches can all change environment behavior. dsh-stack aims to capture this full context and generate a single, portable configuration file.

This is a plugin maintained by weivwang. It declares the environment through a JSON Stackfile, including plugin order, installed registry versions, Git source commit locks, and configuration patches. The file can be used in projects, release notes, or team manuals, and anyone can review it before allowing it to touch configuration files.

Core Features

  1. Capture full configuration: Records plugin order, versions, and configuration patches.
  2. Generate Stackfile: Exports it as a portable JSON file.
  3. Secret management: Manages secrets with placeholders instead of plaintext credentials.
  4. Integrity verification: Includes checksum validation.
  5. inspect tool: Provides the stack_inspect model tool.

Installation and Enablement

First install the CLI:

npm install --global dsh-stack

After installation, add the bundle to the Harness configuration.

Typical Usage

Export environment:

dsh-stack export --profile web --name "research-workbench"

Inspect file:

dsh-stack inspect web.dsh-stack.json

Plan changes:

dsh-stack plan web.dsh-stack.json --profile research

Apply configuration:

dsh-stack apply web.dsh-stack.json --profile research --yes

Plan from URL:

dsh-stack plan https://example.com/research.dsh-stack.json --profile research

Notes

  1. Version requirements: Requires DeepSeek Harness 0.1.0-rc.6 and Node.js 22.19+.
  2. Apply behavior: The apply command requires the --yes flag, and it never removes plugins unique to the target. Existing bundles not named in the Stackfile remain in place after the declaration layer.
  3. Exclusions: The Stackfile excludes session history, credentials, global state, and local workspace files.
  4. Security: Inspect lists the required variables. Review the Stackfile before applying it. It is recommended to use managed credentials or environment references to prevent raw secrets from entering configuration patches.

Summary

dsh-stack solves the environment reproducibility problem by packaging the full contract of a Harness environment (including order, versions, and configuration) into a single file. It provides secure read/write paths through the inspect, plan, and apply commands, and manages secrets using placeholders.