Tianyi Cui
8c32bcf97d
The installed-wheel smoke checks real model tool use and externally verifies the created file, a fresh host-only challenge, the copied receipt, and the unchanged source. DeepSeek can return the requested acknowledgement before a file-details paragraph; requiring it to be the last line makes correct SDK execution fail according to the placement of explanatory prose. Accept the exact acknowledgement on any standalone line, retaining completed turns, model-requested tool calls, exact file bytes, and session-log checks. Replay the observed response through both turns and keep negative coverage for absent or embedded acknowledgements and incorrect files.
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.