2026-07-11 14:08:24 +08:00
# DeepSeek Harness Python SDK
English | [中文 ](README.zh.md )
2026-08-04 00:54:19 +08:00
Python packages for driving DeepSeek Harness as a subprocess. The client SDK communicates with the bundled runtime over newline-delimited JSON-RPC on stdio.
2026-07-11 14:08:24 +08:00
## Packages
| Directory | Dist / module | Role |
|---|---|---|
2026-08-10 19:45:54 +08:00
| [sdk ](sdk/README.md ) | `deepseek-harness-sdk` / `deepseek_harness` | High-level turns API and lower-level JSON-RPC client |
docs(python): make the dsh profile runtime current
Document dsh as the only application launcher across architecture, CLI, SDK, app-boot, Python package, contributor, tutorial, and example references. Explain explicit home selection, profile and patch precedence, persistent external plugin installation, the Node-free runtime path, and the absence of complete-config or ~/.dsh fallbacks.
Record the Python profile-runtime decision and update the active naming, installed-wheel, and SEA packaging notes with precise supersession. Regenerate the configuration catalog and module graph after deleting the carrier, update both reviewed languages and pairing records, and classify the retained standalone Cordis files as lower-level test fixtures rather than launch interfaces.
2026-08-23 14:56:55 +08:00
| [sdk-runtime ](sdk-runtime/README.md ) | `deepseek-harness-runtime-bin` / `deepseek_harness_runtime` | Bundled `dsh` CLI executable and native sidecars |
2026-07-11 14:08:24 +08:00
2026-08-04 00:54:19 +08:00
## Behavior
2026-07-11 14:08:24 +08:00
docs(python): define the standalone minimal profile
Record sdk-minimal as the narrow repository-owned exception to base-first profile composition: callers still launch only dsh and cannot provide an arbitrary Cordis tree, while the shipped bundle may own a complete explicit roster. Cross-link the launcher, profile-bundle, Python-runtime, minimal-agent, snapshot, and telemetry decisions; the supersession audit keeps each older note active because its remaining rationale is independent.
Update the CLI, architecture, Python tutorial/reference, example, runtime-wheel reference, and bundle documentation. The docs distinguish the full sdk profile from sdk-minimal, explain explicit-home/plugin/patch customization, state the minimal permission and persistence choices, and retain the separately packaged web profile and frontend assets for direct dsh use.
Correct dsh-base descriptions to cover base-backed profiles, make SDK startup configuration visible in the generated config catalog, add sdk-minimal to the module graph, and regenerate the base-composition graph. English and Chinese pairs are re-recorded at the exact reviewed contents.
2026-08-24 15:39:43 +08:00
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 ](sdk/README.md ) and [runtime carrier reference ](sdk-runtime/README.md ) own runtime selection, profiles, patches, and external plugin management.
2026-07-11 14:08:24 +08:00
2026-08-04 00:54:19 +08:00
## Contributor workflows
2026-07-11 14:08:24 +08:00
2026-08-05 12:46:38 +08:00
The [Python contributor workflows ](development.md ) cover building runtime artifacts, validating the packages, source-mode development, and distribution.
