TGYD-helige/dsh-pi

Name: TGYD-helige/dsh-pi
Author: TGYD-helige

Plugin插件 Native原生 ⭐ 4 Apache-2.0 Prompts & Skills提示词与技能 Migration & Compatibility迁移与兼容

通过兼容性主机，在DeepSeek Harness中运行受信任的Pi扩展。

Project Overview项目介绍

Edited by Zhiwei Agent (zhiwei)由知微Agent(zhiwei)编辑

TGYD-helige/dsh-pi is a native DSH plugin that lets users run unmodified trusted Pi coding agent extensions directly inside DeepSeek Harness. Unlike source-to-source converters, this plugin acts as a compatibility host that uses Pi’s official loader and ExtensionRunner to preserve original Pi semantics. It maps Pi’s interfaces to DSH agent-scoped tools, commands, messages, attachments, and lifecycle hooks. The current release targets Pi version 0.80.x and DSH version 0.1.5-rc.2, with a narrow peer dependency range because DSH is still in developer preview.

To use the plugin, first install the published dsh-pi-host bundle and any Pi extensions you want to enable into the same DSH profile. You can install local development versions of the plugin by pointing DSH to your local checkout instead of using the published npm package. After installation, you need to edit the profile’s cordis.patch.yml file to add a plugin entry for dsh-pi, list the selected Pi extensions in the config, and adjust settings like strict mode and local path access. This plugin is designed for DSH users who want to leverage the existing Pi extension ecosystem.

This project is released under the open-source Apache-2.0 license, and uses pnpm for dependency management and local development builds. For local development, you need to clone the Pi repository to your local machine and set the PI_FIXTURE_WORKSPACE environment variable to run compatibility tests. Since Pi extensions are unsandboxed Node.js code, allowLocalPaths is disabled by default to prevent unauthorized execution of local code. The npm published package ships prebuilt artifacts, so no build step is required during installation.

dsh-pi 是专为 DeepSeek Harness (DSH) 开发的原生插件，用于在 DSH 环境中直接运行未经修改的可信 Pi 编码代理扩展。它不是源码转换器，而是作为兼容层托管 Pi 的官方加载器和扩展运行器，将 Pi 的语义转换适配为 DSH 作用域内的工具、命令、消息、附件和生命周期钩子。当前版本适配 Pi 0.80.x 和 DSH 0.1.5-rc.2，对 DSH 预览版的版本范围限制较严格。

用户安装该插件后，需要将想要使用的 Pi 扩展和该插件一同安装到同一个 DSH 配置文件中，随后在配置文件的 cordis.patch.yml 中添加插件配置，指定要启用的 Pi 扩展列表，还可以配置严格模式、本地路径允许等选项。完成配置后设置 PI_CODING_AGENT_DIR 环境变量指向配置文件目录，就可以启动 DSH 使用加载的 Pi 扩展能力。它面向需要在 DSH 中复用现有 Pi 扩展生态的 DSH 用户和扩展开发者。

该项目使用 Apache-2.0 许可证，依赖 pnpm 进行包管理和构建，开发阶段需要克隆 Pi 仓库到本地并设置环境变量运行兼容性测试。注意 Pi 扩展是未沙箱化的可信 Node.js 代码，默认关闭 allowLocalPaths 避免未授权本地代码执行，严格模式开启时会在无法适配工具模式时直接报错，关闭则跳过无法适配的工具。npm 发布包自带预构建产物，不需要安装时重新构建。

View on GitHub在 GitHub 查看

Send to your DSH发给你的 DSH 安装

请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：dsh-pi（TGYD-helige/dsh-pi）
仓库：https://github.com/TGYD-helige/dsh-pi
本站详情页：https://www.yhbd.top/plugins/tgyd-helige-dsh-pi/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 Apache-2.0 · ⭐ 4 · 最近提交 2026-09-15 · 主语言 TypeScript

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【1 兼容性检查】
① 我这边：DSH 版本、Node 版本、操作系统、当前 profile（web / desktop）。
② 读它的 README、package.json、插件 manifest，列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对，结论只写「满足 / 不满足 / 未知」三种；不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突：命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。

【2 安全性检查】
① 仓库可信度：和上面「本站登记」是否一致；star / fork 数、创建时间、最近提交，是否归档或长期停更。
② 安装脚本：逐行看 package.json 的 preinstall / install / postinstall，以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名，立刻停下来告诉我，不要继续装。
③ 依赖：列出新增依赖，标出无人维护、或与知名包拼写近似的可疑包（typosquatting）。
④ 权限与副作用：它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限（filesystem / network / shell / clipboard 等），以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限，或权限明显超出功能所需，先停下来问我。

【3 安装】
上面两步没有「不满足」和「高危项」时才执行；用官方推荐方式安装，不要自行提权。

【4 汇报】
用表格输出：检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜，也不要替我决定。

Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH：它会先核对兼容性与安全性（逐条给「满足 / 不满足 / 未知」），确认没问题再安装，有高危项会停下来问你。框内可滚动，复制到的是完整提示词；安装命令不一定准确，发给 DSH 更稳。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 1 warning1 项注意

Only 4 stars - very few users, little community feedback星标只有 4，几乎没人在用，遇到问题缺少社区反馈

DSH walks through these 9 checksDSH 会逐条核对这 9 项

Compatibility兼容性

DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时（Electron / Python / Docker 等）是否齐备
Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突：命令名、skill / tool 重名、端口占用、重复 MCP 注册

Security安全性

Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致，是否归档或长期停更
Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需（filesystem / network / shell / clipboard）
Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限，以及卸载与回滚方式

Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照，不能替代安全审计。

Or use CLI install (for developers)或使用命令行安装（适合开发者）

CLI Install命令行安装

dsh plugin --profile demo add dsh-pi-host \

把 TGYD-helige/dsh-pi 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

16.8 KB · 缓存于 2026-09-11 19:41:33 · 16.8 KB

DSH Pi

Run trusted, unmodified Pi extensions inside DeepSeek Harness. This is a compatibility host, not a source-to-source converter: Pi's official loader and ExtensionRunner own Pi semantics, while this package adapts their observable surface to agent-scoped DSH tools, commands, messages, attachments, and lifecycle hooks.

The project currently targets Pi 0.80.x and DSH 0.1.5-rc.2. DSH is still a developer preview; the peer range is intentionally narrow.

Why a host instead of generated plugins

An extension factory is executable code with lifecycle and session state. Converting its source once cannot preserve tools registered during session_start, mutable active-tool sets, cancellation, providers, or per-agent state. The host therefore creates one Pi runtime per DSH agent and reconciles registrations into that agent's Cordis context.

flowchart LR
  C["DSH bundle config"] --> R["Package / manifest resolver"]
  R --> P["Pi loader + ExtensionRunner"]
  P --> A["Agent-scoped adapter"]
  A --> T["DSH tools"]
  A --> M["DSH commands"]
  A --> L["DSH lifecycle and messages"]
  F["Existing Pi packages\nread-only fixtures"] --> R

Local development

pnpm install
pnpm check
PI_FIXTURE_WORKSPACE=/absolute/path/to/pi pnpm test
pnpm compat /absolute/path/to/pi

The repository at ../pi is only read. Compatibility tests inventory its packages/pi-* manifests and source API usage; representative smoke tests load built entries without calling paid tools.

Install as a DSH bundle

Install the published bundle and the Pi extensions you want in the same profile:

dsh plugin --profile demo add dsh-pi-host \
  @amaster.ai/pi-image-gen \
  @amaster.ai/pi-video-gen
dsh --profile demo --dump-config

For local development, replace dsh-pi-host with the path to this checkout, such as ./dsh-pi when running from its parent directory.

The selected Pi packages must be installed in the same DSH profile so bare package specifiers resolve from that profile. DSH may warn that they declare no dsh.bundle; that is expected because they are plain dependencies loaded by dsh-pi-host, not independent DSH layers. Install any other package named in extensions the same way.

Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要，完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →

渲染基于仓库 TGYD-helige/dsh-pi 的 README.md。在 GitHub 查看原文 →