pi2dsh

When you're on a new platform but want mature tools, you usually face a choice: wait for the community to build the ecosystem, or fork and patch things yourself. DeepSeek Harness is built on ideas worth betting on, but its plugin ecosystem is still early — the plugins people want on day one (web search, memory, code navigation, subagents, vision) mostly aren't written for it yet. Pi already has that ecosystem, and it's mature: hundreds of published packages, many with real users.

pi2dsh approaches this with a single idea: implement Pi's public extension ABI on top of DSH's native services, so a Pi package runs on DSH exactly as published — no fork, no patch, no per-package adapter. You install a Pi plugin the same way you install anything else in DSH, and it works. There's no conversion step, no generated bundle, no build. The engine discovers the Pi packages in your profile and mounts them through a single bridge instance.

As of August 2026, 47 of the top 50 Pi packages by monthly downloads have been exercised successfully through black-box probes, spanning MCP, web search, code navigation, subagents, memory, planning, images, and external integrations. A set of flagship plugins — pi-mcp-adapter, vision and image generation running on real DSH loops, @tintinweb/pi-subagents, and more — have been verified end to end in real DSH sessions. At the same time, the bridge is a full-surface, real-world test of DSH's architecture: wherever a capability must be bypassed or degraded, it pinpoints an architectural gap that remains.

If you're already using DeepSeek Harness and want immediate access to Pi's mature ecosystem — especially MCP, subagents, vision, and memory — or if you're evaluating whether DSH's architectural promises hold up, pi2dsh is for you. It turns ecosystem maturity from a reason to hesitate into a compatibility layer you can just install.