2026-07-11 14:08:24 +08:00
|
|
|
|
# DeepSeek Harness Python SDK
|
|
|
|
|
|
|
|
|
|
|
|
[English](README.md) | 中文
|
|
|
|
|
|
|
2026-08-04 00:54:19 +08:00
|
|
|
|
用于以子进程方式驱动 DeepSeek Harness 的 Python 包。客户端 SDK 通过 stdio 上按行分隔的 JSON-RPC 与内置运行时通信。
|
2026-07-11 14:08:24 +08:00
|
|
|
|
|
|
|
|
|
|
## 包
|
|
|
|
|
|
|
docs(i18n): align single-exe terminology
Add canonical Chinese bindings for build target, deploy root, peer
dependency, serving surface, wheel, wrapper, and VFS so future translations
have one source of truth. Apply the existing runtime, plugin, artifact, and
pipeline bindings throughout every Chinese counterpart touched by this PR.
Require the first Chinese use of peer dependency to retain the English term
so readers can map it back to the package-manager concept without
reintroducing mixed prose throughout the document.
Rewrite mixed-language prose where the English term is not an identifier,
while retaining package names, paths, flags, pkg, single-exe, and other
literal names exactly. Explain VFS on first use and keep technical constraints
readable without inventing compatibility terminology.
Describe single-executable worker support as implemented behavior, including
the filesystem-string entry contract and CommonJS worker artifact required by
the pkg loader, and remove the obsolete bundled-but-unsupported limitation.
Regenerate pairing fingerprints and the generated catalog reference so the
mechanical documentation gates validate the revised English and Chinese
pairs. This keeps the terminology table authoritative and prevents the two
languages from drifting as the runtime documentation evolves.
2026-07-13 21:03:25 +08:00
|
|
|
|
| 目录 | 分发名 / 模块 | 职责 |
|
2026-07-11 14:08:24 +08:00
|
|
|
|
|---|---|---|
|
2026-08-04 00:54:19 +08:00
|
|
|
|
| [sdk](sdk/README.md) | `deepseek-harness` / `deepseek_harness` | 高层轮次 API 与低层 JSON-RPC 客户端 |
|
|
|
|
|
|
| [sdk-runtime](sdk-runtime/README.md) | `deepseek-harness-runtime-bin` / `deepseek_harness_runtime` | 内置运行时二进制与默认 agent（智能体）配置 |
|
2026-07-11 14:08:24 +08:00
|
|
|
|
|
2026-08-04 00:54:19 +08:00
|
|
|
|
## 行为
|
2026-07-11 14:08:24 +08:00
|
|
|
|
|
2026-08-09 03:20:17 +08:00
|
|
|
|
除非调用方选择显式通道，否则 SDK 会启动匹配的内置运行时。客户端负责选择通道和注入默认配置；运行时本身始终要求显式配置。完整的解析与配置约定分别由 [SDK 参考](sdk/README.md) 和 [运行时载体参考](sdk-runtime/README.md) 定义。
|
2026-07-11 14:08:24 +08:00
|
|
|
|
|
2026-08-04 00:54:19 +08:00
|
|
|
|
## 贡献者工作流
|
2026-07-11 14:08:24 +08:00
|
|
|
|
|
2026-08-05 12:46:38 +08:00
|
|
|
|
[Python 贡献者工作流](development.md)介绍运行时产物构建、包验证、源码模式开发和分发。
|