Files
deepseek-harness/python
fz 6e49ccad18 feat(skill): extract the workspace-dependencies tool into a package
Move `load_workspace_dependencies` and the primary-runtime payload logic out
of `apps/desktop-host` into `@deepseek-ai/dsh-tool-workspace-dependencies`
so profiles other than Desktop can mount the same tool. Desktop keeps its
behavior through the package.

Two additions for carriers that are not Electron applications:

- `root` is optional: without it the payload is validated and used in place
  (no copy under the Harness home), which suits read-only container layers.
- `runtime.json` accepts `linux`, and the `node` / `pnpm` components are
  optional; the returned paths and the tool output omit what the payload
  does not ship.

The `sdk` profile mounts the tool and `@deepseek-ai/dsh-skill-office` when
`DSH_PRIMARY_RUNTIME` names a payload directory (its sibling `office-skills/`
carries the skill resources); both rows stay disabled otherwise. Both
packages join the Python runtime closure.
2026-09-17 18:16:47 +08:00
..

DeepSeek Harness Python SDK

English | 中文

Python packages for driving DeepSeek Harness as a subprocess. The client SDK communicates with the bundled runtime over newline-delimited JSON-RPC on stdio.

Packages

Directory Dist / module Role
sdk deepseek-harness-sdk / deepseek_harness High-level turns API and lower-level JSON-RPC client
sdk-runtime deepseek-harness-runtime-bin / deepseek_harness_runtime Bundled dsh CLI executable and native sidecars

Behavior

The SDK starts the matching bundled dsh --profile sdk runtime unless the caller selects another dsh executable or profile. The runnable minimal example selects the shipped standalone sdk-minimal profile; the same runtime also packages dsh web and its frontend assets for separate CLI use. Every launch requires an explicitly selected Harness home; Python never silently reads ~/.dsh. The SDK reference and runtime carrier reference own runtime selection, profiles, patches, and external plugin management.

Contributor workflows

The Python contributor workflows cover building runtime artifacts, validating the packages, source-mode development, and distribution.