pi2dsh

项目详情摘要

pi2dsh English** | 中文 Run the Pi ecosystem's plugins on DeepSeek Harness, unmodified.** pi2dsh `0.25.1` 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. What it does not have yet is a large plugin ecosystem: it is early, and the plugins people want on day one — web search, memory, code navigation, subagents, vision — are mostly not written for it yet. Pi has that ecosystem already, and it is mature: 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. You install a Pi plugin the same way you install anything else in DSH, and it works. 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. Install One engine, then whatever plugins you