pi2dsh plugin
A compatibility layer that runs Pi extension packages on DeepSeek Harness as published, with MCP and subagents
- 220 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Runs third-party npm extension packages with access to your DSH environment
- MCP servers with OAuth run through the layer and carry their own permissions
Install
Manual install
dsh plugin add pi2dsh@nextFor DSH 0.2.2-alpha.3 and Node.js 24.9 or newer; then the Pi packages you need, for example dsh plugin add pi-mcp-adapter. For DSH 0.2.1 use pi2dsh@0.27.1.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Runs third-party npm extension packages with access to your DSH environment
- MCP servers with OAuth run through the layer and carry their own permissions
This is third-party code. Review the repository files before installing.
What it does
pi2dsh implements Pi's public extension ABI on top of DeepSeek Harness (DSH) native services, so Pi packages run on DSH as published, with no fork, patch or per-package adapter. Installation uses dsh plugin add commands: first pi2dsh@next, then the npm packages you need such as pi-mcp-adapter. The MCP path is verified most deeply: the full protocol surface (OAuth, resources, prompts, MCP Apps, elicitation, sampling, cancellation) runs through DSH's own approval and rendering. Web, terminal and headless modes work. The author keeps a version compatibility table and claims only what an end-to-end test verified: version 0.28.0-next.1 targets DSH 0.2.2-alpha.3, and version 0.27.1 targets DSH 0.2.1-rc.2 and rc.3. The author's motive: DSH has a strong foundation but a young plugin ecosystem, while Pi has a mature one with hundreds of packages.
Who it is for. Pi users moving to DeepSeek Harness who want to keep familiar extensions, the MCP manager and subagents.
Good fit when
- A team works on Pi and tries DSH without wanting to change extensions
- You need pi-mcp-adapter and other Pi packages on DSH without forks
- You want MCP with OAuth and resources through DSH approvals
- You want to check Pi and DSH versions against the compatibility table before upgrading
Not a fit when
- Your DSH host version is not in the compatibility table: the author does not claim untested versions
- You only use Pi: the compatibility layer is unnecessary
- A third-party terminal does not declare support for the host version: the preview tests web and headless modes
Example request
Install pi2dsh and pi-mcp-adapter in DeepSeek Harness and connect my MCP servers the way they worked in PiLimitations
Version 0.28 is a preview (next) built for Pi 1.4 with documented limits and needs Node.js 24.9 or newer. The published 0.27.x line uses Pi 0.84.1 and is compatible only with DSH 0.2.1-rc.2 and rc.3. The old dsh-pi-tui 0.5.1 terminal references removed host components; upgrade it and do not bypass the check with the allow-version flag. Only what is in the table of verified capabilities is claimed.
How to disable. Run dsh plugin remove pi2dsh and the same for installed Pi packages. DSH sessions are stored in the host's own format.
FAQ
What are DSH and Pi?
DeepSeek Harness is an agent shell from DeepSeek with a session log and services. Pi is an agent tool with a mature extension ecosystem. pi2dsh gives Pi packages a runtime on DSH.
Which versions are compatible?
pi2dsh 0.28.0-next.1 works with DSH 0.2.2-alpha.3, 0.27.1 with DSH 0.2.1-rc.2 and rc.3, 0.27.0 with rc.2 and 0.26.0 with DSH 0.2.0-rc.2. Version 0.25.2 is frozen as a checkpoint.
How is MCP verified?
Through the full protocol surface: OAuth, resources, prompts, MCP Apps, elicitation, sampling and cancellation. The evidence matrix is in docs/mcp-compatibility.md.
Do Pi packages have to be changed?
No. The layer implements Pi's public extension ABI and packages install from npm as published, with no forks, patches or per-package adapters.
Which terminals were tested?
For the 0.27.x line and DSH 0.2.1 the validated packages are @deepseek-harness-tui/dsh-tui 0.17.0 and @xmoon76/dsh-pi-tui 0.5.3. In the 0.28 preview the web and headless modes are tested independently.
Discussion
No questions or reviews yet.
Related
PluginsDeepSeek Harness is an open-source AI agent from DeepSeek where every feature is a plugin. It runs in the browser, on macOS and on Windows.
A DeepSeek Harness plugin for a standing team of agents with memory, projects, task owners and verification by a second member
dsh-baton hands tasks from Claude Code or Codex to a local DeepSeek Harness and brings the result back with checks.
A DeepSeek Harness plugin that makes the agent change approach after failures and verify results before finishing.
A DeepSeek Harness plugin: Claude Code, Codex, Antigravity and Grok dispatch work to DSH agents, progress in the native task panel
A plugin opening DeepSeek Harness, Codex, Cursor and Claude Code workspaces from a phone or browser over encrypted P2P.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| pi2dsh (this card) | no | 220 | |
| pi-extensions | no | 777 | a set of extensions for Pi, while pi2dsh carries such packages over to DeepSeek Harness |
| DeepSeek Harness | yes | 280,265 | the shell itself, while pi2dsh adds compatibility with Pi packages |
README in short
The README opens with the promise to move a Pi setup to DSH without rebuilding it and a version table. It then explains why the layer exists, lists the capabilities verified end to end and links to each release's acceptance reports in the community folder.