description: "Forked from the official @deepseek-ai/dsh-subagent-codex: makes Pi a first-class citizen in DeepSeek Harness — true-gateway direct connection, queued/steered continuous conversation, live intermediate output, durable binding with auto-reattach, and image passthrough."
kind: "package-bundle"
dsh-subagent-pi-plus
English | 中文
Package-name notice: the npm name `dsh-subagent-pi` belongs to an earlier
third-party project and is not this plugin. This plugin is published on npm as
`dsh-subagent-pi-plus` (`npm install dsh-subagent-pi-plus`) and its home repository is
`february2015/dsh-subagent-pi-plus`.
This plugin is forked from the official @deepseek-ai/dsh-subagent-codex plugin (via the personal dsh-subagent-codex-plus project), switching the direct-connected agent from Codex to Pi — making Pi a first-class citizen inside DeepSeek Harness (dsh).
Relationship with dsh-subagent-codex-plus
dsh-subagent-codex-plus is the sibling plugin of this one: both are personal forks of the official @deepseek-ai/dsh-subagent-codex that add the same true-gateway layer on top — direct connection, queued/steered continuous conversation, live intermediate output, durable binding, and image passthrough. They differ only in the direct-connected agent — Codex in dsh-subagent-codex-plus, Pi here — and share the same architecture, so features, commands, and docs map one-to-one:
| dsh-subagent-codex-plus | dsh-subagent-pi-plus (this plugin) |
|---|
| Direct-connected agent | Codex | Pi |
| Lock command | /codex-lock | /pi-lock |
| Unlock command | /codex-unlock | /pi-unlock |
| Header badge | CDX-xxxx | PI-xxxx |
Both projects live under the same GitHub account and are maintained in parallel. Pick either — or install both; each binds its own sessions and they coexist without interference.
Features
1. True-gateway direct connection (core)
One local command binds your current dsh conversation 1:1 to a durable Pi session; from then on everything you type in the dsh composer goes straight to Pi — dsh runs no model in between, it only relays.
/pi-lock binds the session to a persistent Pi session (an existing Pi session can be resumed by id)./pi-unlock unbinds and restores the normal dsh agent loop; the Pi session is kept and can be rebound anytime.- Durable binding: after shutting down / restarting dsh, reopening the session auto-reconnects the same Pi session, no manual step needed.
- One Pi session can be bound to only one dsh session.
2. Continuous conversation: queue + direct insert
- While Pi is busy, new messages are queued automatically and run in order when the current turn ends.
- The floating panel can insert a message directly (it runs ahead of queued messages on the next turn).
- The queue is fully manageable: view, promote, insert, edit, delete.
3. Live intermediate output
Pi's execution progress (message deltas, tool calls, status events) shows up in the dsh session in near real time — not just the final answer. By default it is display-only and never enters the dsh model context.
4. Status display
Once bound, the session header shows a PI-xxxx badge (colored status dot + first 4 session id chars) and the composer dock shows a "Pi 直连 · …" status line. Unbound sessions show nothing, keeping the UI clean.
5. Image / attachment passthrough
Paste or upload images and hand them to Pi as-is. Vision fallback is handled by the TeamAI skill ocgw-vision (this plugin does no vision understanding).
6. Delegation and gateway coexist
One dsh conversation can use model-triggered one-shot Pi delegations and a user-attached gateway session at the same time, without interference.
Quick start
Install
dsh plugin --profile <name> add /path/to/dsh-subagent-pi
dsh --profile <name>
Prerequisites: pi installed and configured (login/model) on this machine.
Usage
- Open any dsh session (cwd is your project).
- Type
/pi-lock: after binding succeeds the header shows a PI-xxxx badge, and input goes straight to Pi.
- While Pi is busy, further messages queue automatically; use the floating panel to view/promote/insert/edit/delete.
/pi-unlock disconnects; the Pi session is kept and can be rebound with /pi-lock <piSessionId>.
Docs
IMPLEMENTATION.md — feature checklist (implementation details)REQUIREMENTS.md — requirements specTECH-VERIFICATION.md — technical verification report (implementation technology)
