dsh-session-tree-extension
用于 dsh-session-tree 插件包的开发工作区（未发布）
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:robiteame/dsh-session-tree-extension#cee5773721b43838799fa6dcae124d1ec9e0b9c4
Session Tree Extension 以 dsh-session-tree-extension 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Append-only, multi-branch conversation trees for DeepSeek-Harness — a PI-Agent-style SessionTree. The agent's history becomes a tree of immutable nodes, forkable at any historical node, with standard LLM message reconstruction, versioned JSON snapshots, and a WebUI tree panel.
Published as four npm packages under the @robiteame scope:
| Package | Role |
|---|---|
@robiteame/dsh-session-tree | Carrier Bundle: one install mounts everything below through its composition layer |
@robiteame/dsh-pi-agent-session-tree | Host domain service: SessionTree/SessionTreeStore, JSON snapshots, the sessionTree Remote (list/jump/fork/session) |
@robiteame/dsh-tool-session-tree | Model-facing surface: the session_tree tool, /tree /fork /clone /session commands, system-prompt section |
@robiteame/dsh-client-ui-session-tree | WebUI tree panel: additive right-side overlay on official builds, native details dock on patched builds |
One command — from the plugin market UI, or from a Harness checkout's CLI:
dsh plugin --profile <profile> add @robiteame/dsh-session-tree
Prebuilt tarballs install the same way and need no build scripts:
dsh plugin --profile <profile> add robiteame-dsh-session-tree-0.1.0.tgz
After installing, restart the profile. The composition gains three rows
(pi-agent-session-tree, tool-session-tree, ui-session-tree) that load the
Host service, the tool and commands, and the browser panel. Type /tree in the
composer to open the panel; click a node to bind it as the active context, then
/fork [branch] and /clone operate on that selection. /session reports
tree status (nodes/messages/branches/tokens/cost) and the active surface mode.
Verify the composed layer:
dsh --profile <profile> --dump-config # should list the three session-tree rows
Requires DeepSeek-Harness 0.1.2-alpha.3 (or a compatible 0.1.2 build) and
Cordis ^4.0.2; the target installation provides those peers. No install
scripts run — the tarballs ship prebuilt lib/ artifacts.
The plugin never modifies Harness core files. It capability-detects the optional branch-selection engine API at runtime:
dev/session-branch-surface.patch
(Session.selectMessageSurface()), jump/fork switch the model-visible
history directly: the next turn genuinely starts from the new branch.replace surface event) plus a
plugin-owned sidecar under $DSH_HOME/storages/session-tree/ for durable
branch state. The log stays resume-valid.Every mode is honest about itself: session_tree's context/session
operations and /tree outputs carry a surface field (native, stock, or
projection), and the Host log prints a one-time notice when a session runs in
a non-native mode. Move the raw session.jsonl.zstd between machines together
with the matching sidecar file, or carry the projection explicitly with
/tree snapshot save/load.
message, tool_call, model_change, compaction, branch_summary,
custom; tool_result survives only for orphan results with no matching
call); each has a unique nodeId and a parentId (root is null). A node
may have multiple children — that is the fork.tool/call and its tool/result fold
into a single tool_call node whose content carries both the call part and
the result part (isError plus the node's error mark failures), whether
the pair arrives in one event batch or across sync batches. Legacy snapshots
with split pairs fold on restore.jump(nodeId) moves the active leaf to a historical
node; the next append grows a new branch from there. Sibling branches stay
intact. The durable Harness Session log remains the source of truth.context returns the standard messages array for the
root→cursor path only.compaction
node instead of pretending the shadowed messages were deleted.snapshot.save/snapshot.load round-trip the whole tree as
versioned JSON (version: 1).{ok: true, value} or
{ok: false, error: {code, message}}.The repository is a pnpm workspace building the three implementation packages standalone (no Harness checkout needed):
pnpm install
pnpm verify # build + typecheck (host & client) + pack dry-run + vitest
pnpm pack:all # produce the four tarballs
Tests run against the published Harness packages (0.1.2-alpha.3) — the
stock-mode paths — with vitest from the repository root. The browser spec in
packages/client/ui-session-tree needs the Harness client test runtime and
runs inside a source-integrated checkout.
For debugging against Harness source (native mode, native details dock):
dev/install.sh /path/to/deepseek-harness # applies both dev patches + copies packages
cd /path/to/deepseek-harness && pnpm install && pnpm run build
See dev/README.md for what each patch does. This flow is
for contributors only — user installs never touch a Harness checkout.
MIT.