dsh-pathfinder
把 agent-pathfinder 的管线搬进 DSH：宿主半身按当前会话的工作区读那份记录，交给浏览器半身
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:infraredsqy/dsh-pathfinder#4ade79caca76d314c39b02895665d1b965406dfcPathfinder 以 dsh-pathfinder 发布，当前版本为 0.1.0-rc.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 中文
dsh-pathfinder is a DeepSeek Harness plugin
that renders an agent-pathfinder record as a
panel in the DSH Web UI.
The host half reads the record (.pf/) of the current session's workspace and serves it behind a
gateway; the browser half draws it as the Pathfinder Center panel in the sidebar. Everything on screen —
instructions, node details, the map of who owes whom, the issue pool — comes from that record, and
writes from the panel go back to the same place.
Early, and tied to the DSH developer preview. The manifest declares an engines.dsh range, and DSH
refuses to install or boot the plugin outside that range (incompatible-version, with an opt-in
exemption command). The range moves as DSH does.
The record it draws comes from agent-pathfinder, which is early and moving fast too: expect breaking changes on that side.
Prerequisites: a DSH install with a profile to install into, and a workspace that holds an
agent-pathfinder record (.pf/, with pf on your PATH). The panel reads the workspace of the
session you have selected; with no session selected it says so.
Download the .tgz from this repo's Releases
and point DSH at the file:
dsh plugin --profile <name> add ./dsh-pathfinder-<version>.tgz
dsh plugin --profile <name> add dsh-pathfinder # the same artifact, by name (npm)
The package ships prebuilt — installing runs no build steps. pnpm may print a few missing peer
warnings: those packages are provided by DSH itself and resolve at runtime, so the warnings can be
ignored. The version policy and the third route (installing from git) live in
docs/publish.md.
dsh --profile <name> --dump-config, and look for the
# == dsh-pathfinder sectionpnpm install --frozen-lockfile
npm test # unit tests; builds lib/client.js first, then mounts it in jsdom
node tools/css-check.mjs # the style-layer rules
npm pack # the distributable
npm test covers the model layer, the host half and the built browser half — the last one mounts
lib/client.js over an in-memory record, walks every pane, and fails on any console.error. What it
cannot reach (the readings over a real .pf, the copy, the layout) is on the hand pass in
docs/publish.md; tools/testbed/ boots an isolated DSH instance to walk it.
The repository map and ground rules live in AGENTS.md. Read docs/design-principles.md before touching the UI, and docs/publish.md before shipping a version.