weijiafu14/pi2dsh

Name: weijiafu14/pi2dsh
Author: weijiafu14

Plugin插件 Native原生 ⭐ 212 MIT Migration & Compatibility迁移与兼容 Notifications & Remote通知与远程

打通 Pi 与 DeepSeek Harness 生态系统：一个 Pi 主机 ABI 即可将未修改的 Pi 扩展作为原生 DSH 插件运行。

Project Overview项目介绍

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

pi2dsh is a native DSH plugin that acts as a compatibility layer for running unmodified Pi ecosystem plugins directly on DeepSeek Harness. It implements Pi’s public extension ABI on top of DSH’s native services, so no forking, patching, or per-plugin adapters are required to run published Pi packages. Installation follows standard DSH workflow: users run dsh plugin add pi2dsh to install the core engine first, then can add any Pi plugin from npm directly using the same standard DSH command. Version 0.25.1 targets Pi 0.84.1 and supports specific DSH release versions, with compatibility records hosted in the project repository.

This plugin is designed for DSH users who want access to the mature Pi plugin ecosystem, which already includes hundreds of published packages for common use cases like web search, memory, and code navigation. Typical daily workflow after initial installation is straightforward: adding a new Pi plugin just requires running dsh plugin add <package-name> and restarting DSH for changes to take effect. Upgrading individual Pi plugins leaves the core pi2dsh engine untouched, and upgrading the engine does not affect any installed Pi plugins. Users can also run a compatibility check on a plugin before upgrading, via the built-in npx pi2dsh inspect command.

pi2dsh is released under the open-source MIT license, and requires Node.js 22.19 or newer and a working DeepSeek Harness installation to run. During installation, users may encounter an error from pnpm that blocks dependency build scripts by default, which requires running pnpm approve-builds or updating the pnpm configuration to resolve. Cross-version migration of saved user data is not supported in the current release, and all tested compatibility cases are documented in the project’s version acceptance records.

pi2dsh 是专为 DeepSeek Harness (DSH) 开发的原生兼容性插件，核心作用是让 Pi 生态系统的未修改插件直接在 DSH 上运行。它实现了 Pi 的公开扩展 ABI，基于 DSH 原生服务运行，用户可以像安装其他 DSH 插件一样直接从 npm 安装任意 Pi 插件，无需分叉、补丁或单独适配。当前 0.25.1 版本适配 Pi 0.84.1，支持特定版本范围的 DSH。

它面向需要扩展 DSH 功能的用户，典型工作流是先通过 DSH 命令安装 pi2dsh 引擎，重启 DSH 后就可以直接安装任意需要的 Pi 插件。添加、移除、升级 Pi 插件都通过标准 DSH 命令完成，升级引擎不影响已安装的 Pi 插件，用户还可在安装前检查插件兼容性，支持配置开启原生子代理挂载。

该项目基于 MIT 许可证开源，要求运行环境满足 Node.js 22.19+ 和已安装 DSH。安装时可能遇到 pnpm 默认阻止依赖构建脚本的问题，用户需要手动批准构建或修改配置文件。跨版本已保存数据的迁移不在当前版本支持范围内，所有测试过的兼容性情况都记录在项目的版本验收文档中。

View on GitHub在 GitHub 查看

Send to your DSH发给你的 DSH 安装

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

插件：pi2dsh（weijiafu14/pi2dsh）
仓库：https://github.com/weijiafu14/pi2dsh
本站详情页：https://www.yhbd.top/plugins/weijiafu14-pi2dsh/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 212 · 最近提交 2026-09-22 · 主语言 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兼容性 · 安全性 no risk signal found未发现风险信号

This site's static screen found no obvious risk signal (stars, license, activity, manifest)本站静态筛查没发现明显风险信号（星标、许可证、更新活跃度、清单完整度）

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 web add pi2dsh

把 weijiafu14/pi2dsh 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

32.6 KB · 缓存于 2026-09-22 19:39:04 · 32.6 KB

pi2dsh

English | 中文

Move a Pi setup to DeepSeek Harness without rebuilding it. The extensions, MCP manager, subagents, memory and background tasks you use on Pi install on DSH as the same npm packages and run unmodified — web, terminal and headless.

dsh plugin add pi2dsh            # once
dsh plugin add pi-mcp-adapter    # then the Pi packages you already use, straight from npm

MCP is the deepest-verified path: the full protocol surface — OAuth, resources, prompts, MCP Apps, elicitation, sampling, cancellation — runs through DSH's own approval and rendering (evidence matrix). What has been verified end to end is listed in What actually works today; nothing outside that table is claimed.

pi2dsh 0.25.2 targets Pi 0.84.1 and uses one engine for DSH 0.1.1-rc.2 and 0.1.5-rc.1 / 0.1.5-rc.2. Exact tested workflows and exclusions are in the version acceptance record and rc.2 checks. Cross-version saved-data migration is outside this release.

Why this exists

DeepSeek Harness is built on ideas worth betting on — a durable, reconstructable session log, a clean service composition, an agent loop you can actually reason about. Its plugin ecosystem is young. Pi has a mature one: hundreds of published packages, many with real users.

pi2dsh is one compatibility layer that implements Pi's public extension ABI on top of DSH's native services, so a Pi package runs on DSH as published — no fork, no patch, no per-package adapter. For a Pi user or team that means switching hosts without rebuilding the toolchain; for a Pi plugin author it means a second host with no port to maintain. To the user everything looks like DSH; to the plugin everything looks like Pi.

At the same time, pi2dsh is an ongoing, full-surface, real-world test of DSH's architecture. Instead of patching individual plugins, it asks whether the models, tools, sessions, interaction, resources and client capabilities that Pi plugins rely on can preserve their logic and lifecycle using only DSH's public services and extension seams. If they can, that is strong evidence that DSH's architectural goals for building agents and an agent-plugin ecosystem have been achieved, at least along this dimension. Wherever the bridge must bypass, degrade or cannot express a capability, it pinpoints an architectural gap that remains.

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

渲染基于仓库 weijiafu14/pi2dsh 的 README.md。在 GitHub 查看原文 →