Dsh-dev
August 22, 2026 · View on GitHub
A lightweight control layer for developing out-of-tree DeepSeek Harness plugins. It gives humans and agents reusable development skills, a pinned upstream checkout, version-drift checks, plugin gates, and session-log diagnostics.
DeepSeek Harness is in developer preview and may introduce breaking changes. This repository pins the analyzed upstream commit in
upstream/deepseek-harness.lock.json. Do not combine current documentation with dependencies from a different preview release.
Quick start
Requirements: Git, Python 3.11+, and Node.js 22.19+. Real plugin development also needs pnpm and the dsh CLI.
git clone https://github.com/vimalinx/Dsh-dev.git
cd Dsh-dev
python3 tools/harness_upstream.py sync --locked
python3 tools/check-harness-drift.py
Place independent plugin repositories in dsh-<name>/ directories. The root repository ignores
them so each plugin keeps its own history:
python3 tools/find-dsh-plugins.py --query terminal
python3 tools/check-plugin.py dsh-my-plugin --conformance
python3 tools/check-plugin.py dsh-my-plugin
The shared workflow follows the upstream architecture: capabilities are plugins, composition lives in ordered configuration layers, registrations are reversible effects, model-visible state is reconstructable from the append-only session log, and tool values remain distinct from model and UI presentation.
Third-party checkouts, generated documentation snapshots, independent plugins, .ai/ evidence,
scratch files, machine-local inventory, and real session data are intentionally excluded from the
public repository.
The versioned analysis and workspace decisions are documented in
docs/deepseek-harness-analysis.zh.md.
Upstream and license
This is an independent community project and does not redistribute DeepSeek Harness source code. DeepSeek Harness is published by DeepSeek under its own MIT license and notices. Original material in this repository is available under the MIT License.
Community
This project is promoted in the LINUX DO open-source community. Thanks to the community for discussion, feedback, and suggestions.