工具概览
zDSH-Go 是 zDSH 的发行版，而 zDSH 是 DeepSeek AI 开源智能体框架 DeepSeek Harness 的增强分支。它被描述为“对上下文处理做了重大调整的 zDSH”。关键区别在于，上下文缓存管理是在核心源码层面集成的，因此无法以插件形式发布；zDSH 的其他部分保持不变。
上下文调整应用于核心源码，包括智能体循环、会话处理与投影、工具、token 计量、模型槽位、压缩和子智能体。这意味着上下文缓存管理是核心的一部分，而非外挂插件。具体改动包括：覆盖所有请求路径的核心级上下文缓存管理，携带运行时上下文快照的子智能体提示词，fork 和团队成员以未播种状态启动，通过 l3.pruning 元数据可观测的上下文裁剪，以及通过 scripts/verify-budget-table.ts 实现的常设预算关卡。
zDSH-Go 仅附带官方的树内包（plugin-governance、plugin-project-root）以及树内 Workbench 客户端，其余插件通过治理渠道安装。自研插件不随出厂捆绑；需通过 zDSH 主线及其插件治理渠道获取。安装是自包含的，所有数据都保存在仓库目录内，后备主目录为 ~/.dsh-zdsh-go。
它以源码形式分发，提供适用于 Windows 和 macOS/Linux 的安装程序。上游框架处于开发者预览阶段并快速迭代，因此会出现破坏兼容性的变更。
定价
价格与限制可能变化，请以官网为准，并确认币种、付款周期、最低席位数和用量上限。
应用场景
- 开发者用 zDSH-Go 运行在核心源码层面集成了上下文缓存管理的智能体框架。
- 团队用 zDSH-Go 通过 zDSH 治理渠道安装插件。
- 用户用 zDSH-Go 运行自包含的安装，所有数据都保存在仓库目录内。
- 开发者用 zDSH-Go 在本地启动 Web UI。
- 团队用 zDSH-Go 与现有的官方 DeepSeek Harness 安装共存。
功能特性
出厂集成 Workbench 插件
内置 FileHub 插件
随附 PluginCenter 插件
集成 AutoPilot 功能
包含 WebStack 组件
内置 Omnivision 和 ContextManagement
用户评论
还没有评论，来分享你的使用体验吧
常见问题
How does zDSH-Go relate to the zDSH main line?
zDSH-Go is zDSH plus the context adjustment applied at the core source level. The main line hosts the self-developed plugin suite and upstream tracking; zDSH-Go follows the main line and re-applies the context adjustment. They install independently and can coexist, with separate fallback homes.
Where do the self-developed plugins come from?
From the zDSH main line, through its plugin governance channel. pluginGovernance.install resolves pinned npm sources with a confirmation-gated admission flow. zDSH-Go ships no bundled plugins; only official plugin-governance and plugin-project-root are in-tree.
How do I update?
git pull the default branch, then re-run the installer for your platform. The installer re-installs dependencies with a frozen lockfile and rebuilds. Your data/ directory stays in place.
Why is the context adjustment a source-level integration instead of a plugin?
Because it changes core behavior — the agent loop, session handling, token metering, compaction — it is applied directly to the core source rather than mounted as a plugin. A plugin can only sit beside the core; cache management has to be inside every path the core owns.
Does it conflict with an existing official DeepSeek Harness installation?
No. Official-release data lives in ~/.dsh and is never written to by zDSH-Go's self-contained layout; the uninstaller only touches it after explicit confirmation, and never deletes ~/.agents.