@huanghanheng/dsh-ui-turn-rail
DeepSeek Harness Web GUI 的回合进度栏插件：在对话滚动区域上方显示固定的点状条，提供每回合问题摘要、一键加载深层历史记录和 AI 选项摘要
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add @huanghanheng/dsh-ui-turn-rail@0.1.3Ui Turn Rail 以 @huanghanheng/dsh-ui-turn-rail 发布，当前版本为 0.1.3。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Turn progress rail plugin for the DeepSeek Harness Web GUI: a sticky dot strip pinned to the conversation scrollport, one dot per loaded turn, with per-turn question summaries, one-click deep history loading, and summaries for AI-option picks.
GitHub topics: dsh-plugin · deepseek-harness
user nodes) and picked AI options (steering nodes) produce summaries.ChatSnapshot; the rail holds no session state of its own.A DeepSeek Harness checkout (or the published @deepseek-ai/dsh-* packages) with the host instrumentation applied — the rail registers into the conversation.chat.rail seat that ui-conversation's chat view must declare (see below). Without the seat, the plugin loads but renders nothing (the seat renders fallback: null).
The plugin supports two installation routes. Neither automates the host instrumentation — that is a source-level patch to the harness checkout (see Host instrumentation) and must be applied and rebuilt regardless of how the package is installed.
dsh plugin (recommended)This repository is a DSH bundle: its package.json declares dsh.bundle.patch → ./cordis.patch.yml, so the profile plugin manager installs it as a patch layer and the patch inserts the plugin into the web profile's browser roster.
# From the git repository (no npm publish needed):
dsh plugin --profile web add @huanghanheng/dsh-ui-turn-rail
# Or, once published to npm (shorter spec):
dsh plugin --profile web add @huanghanheng/dsh-ui-turn-rail
dsh plugin runs pnpm add in the profile directory and reconciles dsh.profile.bundles automatically: a dependency whose manifest declares dsh.bundle.patch joins the layer stack.
Then apply the host instrumentation to the checkout the profile runs from — the seat must exist for the rail to render. A ready-made patch ships in this repository, applied in one command (then rebuild the web client):
scripts/apply-instrumentation.sh /path/to/harness-checkout
(cd /path/to/harness-checkout && pnpm run build)
The package publishes to npm with build artifacts committed (lib/), so it installs like any package:
# In the profile directory the app runs from (or the app itself):
npm install @huanghanheng/dsh-ui-turn-rail
# or: pnpm add @huanghanheng/dsh-ui-turn-rail
A manual npm install does not add the bundle layer automatically — declare it in the profile manifest so the patch inserts the plugin row:
// $DSH_HOME/profiles/web/package.json
{
"dependencies": { "@huanghanheng/dsh-ui-turn-rail": "^0.1.0" },
"dsh": { "profile": { "bundles": ["@huanghanheng/dsh-ui-turn-rail"] } }
}
Or simply run dsh plugin --profile web add @huanghanheng/dsh-ui-turn-rail, which performs the install and the bundle-layer reconciliation for you (equivalent to Route 1).
Then apply the host instrumentation and rebuild, exactly as in Route 1.
The seat declaration lives in ui-conversation's slot contract, and the jump/paging gestures must operate ChatView's private scroll anchoring — neither can be delivered as a plugin, so dsh plugin add cannot automate it. The repository ships the exact change as patches/chat-rail-seat.patch (against harness master b150a551b8); apply it with scripts/apply-instrumentation.sh or git apply --3way, then rebuild. If your checkout has drifted, hand-apply the edits below. These are the exact changes:
packages/client/ui-conversation/src/client/contract/slots.ts'conversation.chat.rail': { kind: 'single'; scope: 'session'; owner: ChatTurnRailOwnerProps }
export interface ChatTurnRailOwnerProps {
currentTurn: number | undefined
loadingOlder: boolean
hasMore: boolean
onJump: (key: string) => void
onLoadOlder: () => Promise<void>
}
'conversation.chat.rail' to the PropsRenderSlots union in ChatViewSlotProps.loadOlder: () => Promise<void>
packages/client/ui-conversation/src/client/apply.tsDeclare the seat in the chat view entry's children:
children: {
'conversation.chat.node': { kind: 'keyed', scope: 'session', inject: CHAT_NODE_INJECT },
'conversation.message.images': { kind: 'single', scope: 'session' },
'conversation.chat.rail': { kind: 'single', scope: 'session' },
},
packages/client/ui-conversation/src/client/chat/ChatView.tsxconst chat = useSession(s => s.chat)
const turnByKey = useMemo(() => {
const map = new Map<string, number>()
for (const turn of chat.timeline.turnOrder) {
for (const key of chat.locations.getTurn(turn)) map.set(key, turn)
}
return map
}, [chat])
currentTurn in the scroll handlers (set it from turnOf(anchorKey) or the latest turn when pinned to the bottom).loadOlderAnchored returns the paging promise:
const loadOlderAnchored = (): Promise<void> => {
// ...existing paging-anchor logic...
return loadOlder()
}
{renderSlot('conversation.chat.rail', {
currentTurn,
loadingOlder,
hasMore,
onJump: jumpTo,
onLoadOlder: loadOlderAnchored,
}, { fallback: null })}
pnpm install
pnpm vitest run tests/ # unit tests (model + component, jsdom)
pnpm bundle # tsdown client bundle (needs the harness's clientBundle preset)
The tests cover the turn model (tick derivation, typed/AI-option summaries, placeholders) and the component (jump, one-click paging past page boundaries, active-dot follow, window scroll).
MIT