English | 简体中文
The open-source DSH companion plugin for DeepPilot, a native iPhone client for using DeepSeek Harness remotely. It connects the app directly to the DSH Host on your own computer and does not replace or modify the DSH Web UI.
DeepPilot is currently in TestFlight review. The invitation link will accept testers after Apple approves the build.
- Browse projects, sessions, history, and live agent output from iPhone.
- Stream assistant text and reasoning while viewing a session; reconnects recover the durable history rather than treating partial output as a completed answer.
- Export a full ZIP log archive, or share the conversation body as Markdown when the Host provides that optional route.
- Check plugin updates from the app and install an explicitly confirmed compatible version. The Host handles hot replacement and rollback; without hot reload the app reports that a DSH restart is required.
- Send prompts, switch models, create sessions, and answer approvals/questions.
- Pair with a five-minute single-use code and a per-device P-256 key; physical iPhones keep the private key in Secure Enclave.
- Connect over the LAN (TLS with a Host-issued certificate pinned during pairing) or the optional embedded Tailscale Funnel.
- Receive live notifications and optional APNs notifications while offline.
- Self-update hint: the settings page footer shows the installed plugin version, with an inline "new version" link to the matching GitHub release when one exists (background check, stable releases only, no third-party dependency).
This source checkout targets Node.js 22+ and the eight DSH releases it has been
audited against — 0.2.0-rc.2, the alpha channel releases 0.2.1-alpha.3,
0.2.1-alpha.4, 0.2.1-alpha.5, and 0.2.2-alpha.2, and the next channel
releases it has admitted in turn, 0.2.1-rc.2, 0.2.1-rc.3, and 0.2.1-rc.4 —
with a web profile. (The npm channels move: latest now points at
0.2.1-rc.2, which was promoted from next, next at 0.2.1-rc.4, and
alpha at 0.2.2-alpha.2.) DSH checks a plugin's declared
requirements before composing a profile, on every start rather than only on
install, so any other host version refuses to activate this plugin. From DSH
0.2.1-alpha.4 on, that check reads engines.dsh and ignores
peerDependencies; older hosts know only the peer range, so both name the same
eight releases. The package includes Funnel helpers
for macOS, Linux, and Windows on amd64/arm64; trusted-LAN mode does not require
the helper. The helper is built with Go 1.27, which requires macOS 13 Ventura
or later: on macOS 12 and earlier, Funnel mode cannot start, while
trusted-LAN mode keeps working.
The current working tree names exactly those six versions in engines.dsh and
peerDependencies and is built/typechecked against 0.2.0-rc.2. A previously
published plugin package may still carry its own older compatibility
declaration until a release is made from this tree.
dsh plugin --profile web add dsh-deeppilot
dsh webAfter DSH restarts, open Settings → DeepPilot, enable the connection, show the pairing QR code, and scan it in the DeepPilot app. Below the QR code the same panel shows one copyable piece of pairing info (address, single-use code and certificate fingerprint) that can be pasted into the app in one step — useful for Simulator or when the camera is unavailable. Switching between the LAN and public address issues a matching new QR code and string immediately, with the panel staying open.
LAN access is enabled by default on the plugin's independent TCP port 3098
and is TLS-only. The plugin generates a self-signed certificate on first start
(key under $DSH_HOME/deeppilot/lan-tls/), and the pairing QR code carries its
public-key fingerprint so the app pins that exact Host. DSH may continue
listening only on 127.0.0.1:3080; the plugin no longer registers any /phone
routes on the DSH web server. If a firewall is enabled, allow inbound TCP
3098 on the networks you use. The port can be changed on the DeepPilot
settings page (its exact section may move between DSH versions; go by the
settings page's current layout).
Upgrading from a plugin version that served plain ws:// on the LAN: devices
paired over the LAN must pair again so they receive the certificate
fingerprint. Devices paired through Funnel are unaffected.
Package: npmjs.com/package/dsh-deeppilot
dsh plugin --profile web update dsh-deeppilot
dsh plugin --profile web remove dsh-deeppilotRestart DSH after updating. Uninstalling the package does not delete the local
DeepPilot state under $DSH_HOME/deeppilot/.
采用可信发布（Trusted Publishing）：GitHub Actions（GitHub 工作流）通过 OIDC 身份认证发布，并生成来源证明（Provenance），无需长期 npm 发布令牌。
- 同步包版本与锁文件版本，按
AGENTS.md完成发布验证；提交、推送并等待 持续集成（CI）通过。 - 从已合入
main的发布提交创建附注标签v<版本>，准备英文与简体中文的 GitHub Release（发布页）草稿。 - 经用户授权后，在该版本标签上手动运行
publish.yml。稳定版使用latest（稳定分发标签），预发布版使用alpha（预发布分发标签）。 - 核对 npm 版本、分发标签、包完整性与来源证明，并在全新 DSH 配置中安装验证， 然后公开 GitHub 发布草稿。
工作流不会因推送标签自动发布。npm 网站绑定、手动命令及首次发布的验证边界见 npm 可信发布说明。
Conversation traffic travels directly between the iPhone and your DSH Host and
is always encrypted: the LAN listener on port 3098 serves TLS with a
self-signed certificate whose fingerprint the app receives during pairing, and
Funnel mode uses Tailscale-issued certificates. The app refuses plain ws://.
Both the LAN listener and optional Funnel mode expose only the DeepPilot
connection, one-time pairing, and health endpoints, not the complete DSH Web UI.
The DeepPilot settings page exposes Connections per public source. It
defaults to 8, accepts 1–16, and briefly restarts the Funnel helper when
changed, so connected remote clients reconnect once (its exact section may
move between DSH versions; go by the settings page's current layout). The
device list also supports a custom name for each paired device. Names are
stored in the host registry and survive iPhone reconnects or changes to the
system-reported name; saving an empty value restores the iPhone-reported
default.
The settings page's Testing & troubleshooting group has a debug toggle.
Turning it on prints per-frame and push diagnostics to the DSH host's terminal
output (for example, the actual capability bits sent in s2c.welcome); it
never prints pairing tokens, APNs tokens, or message content. The toggle is
snapshotted per connection, so an already-open connection only picks up the new
value after it reconnects.
Connection failures do not need that toggle. The plugin always records
admission rejections, authentication failures (4401 distinguishes an unknown
device, a revoked device, a bad signature, an expired challenge and clock skew),
TLS handshake failures and pairing failures. They show up in the terminal as
[deeppilot] <time> WARN <event> <reason> src=<source hash> attempt=<attempt ID>
and are appended under diagnostics/ in the plugin data directory (7 days,
5 MB cap). The settings page's Connection diagnostics group lists the most
recent failures with a copy button, and /phone/health additionally returns the
local transport phase and port, the data-plane phase, whether the TLS identity
was rebuilt, the start time and the last failure, so the phone can locate the
cause even while it cannot connect. Records contain only source hashes — never
raw IPs, pairing codes, keys, APNs tokens or message content.
Each connection attempt from the phone carries a random attemptId (the ?at=
query parameter on the WebSocket upgrade, or the X-DeepPilot-Attempt header on
pairing and health checks). The plugin writes it into the log lines and
diagnostic events above, so a user reporting that ID lets you find the exact
attempt in the host log.
Offline push is optional. Relay mode sends only the target APNs device token and a limited notification payload; full conversation history and live output do not pass through the relay. Read PRIVACY.md and SECURITY.md before enabling remote access or push. Protocol-v2 implementation status and remaining release validation are tracked in docs/SECURITY_ROADMAP.md.
| Home | Sidebar | Chat | Settings |
|---|---|---|---|
 |
 |
 |
 |
See COMPATIBILITY.md for the tested baseline and current limitations. DSH is still evolving; include exact DSH and plugin versions when reporting an issue.
PROTOCOL.md is the normative DeepPilot bridge protocol. Any
wire change must update that document and src/protocol.ts together and be
coordinated with the private iOS client. Protocol v2 is the only supported wire
version; upgrades from v1 require re-pairing.
npm ci
npm test
npm run typecheck
npm run build
cd helper && go test ./...DeepPilot is an independent community project and is not affiliated with or endorsed by DeepSeek.
MIT — see LICENSE.