dsh-bonsai
Bonsai (盆栽) — DeepSeek Harness 的可编辑对话树：分支编辑和回收站、规则编辑器、精确的令牌统计、工具裁剪以及零调用历史折叠。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-bonsai@0.1.12Bonsai 以 dsh-bonsai 发布，当前版本为 0.1.12。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A conversation-tree editor for DeepSeek Harness, plus two switches that really do save tokens.
简体中文 · English
A conversation is drawn as a tree: questions, answers and tool results are nodes you can fork, re-parent, hide, recycle, and jump back to in order to keep growing from an earlier point. The tree also carries exact token accounting, and two ways to keep what no longer belongs out of the model's view.
dsh-bonsai · DeepSeek Harness plugin · no runtime dependencies · MIT · Node ≥ 24
Every number below is measured, not estimated. The raw records live in
docs/experiment-context-cache.md.
| Capability | Status | Measured |
|---|---|---|
| Hide tools | Optional (nothing hidden by default) | 37 → 28 tools: 10,453 → 7,076 tokens/turn (−32%) |
| Fold history | On by default, from 40,000 tokens | Controlled 4 turns: 15,341 → 12,906 tokens (−16%), zero model calls |
| Effect of folding on the cache | — | Hit rate 98.2% (98.5% unfolded): no collapse |
| Graphical tree editing / recycle bin | Done | Fork, re-parent, hide, restore, jump, compare branches; cancelled turns leave the tree on their own |
| Rule editor | Done | Hand-written and auto-detected rules as chips, add/edit/delete, sent with the retrieval hint |
| Exact token accounting | Done | Official tokenizer; falls back to the bill when no vocabulary is available |
Retrieval gain (retrieve_context) | Not proven | Five experiments found no recall benefit; off by default |
Requires DeepSeek Harness (the desktop app or the dsh CLI). Quit the desktop app completely
before installing.
dsh plugin --profile desktop add dsh-bonsai
After a restart a 🌳 Bonsai panel sits above the composer, and a “Bonsai” button appears in the session header.
Local development (no npm):
pnpm install; pnpm run build; node scripts/stage.mjs
dsh plugin --profile desktop add "file:<repo>/plugin"
Do not point a
link:at the repository root — the desktop app treats that root as a workspace and scans it.
83% of the prompt's characters are tool definitions. The “hide tools” panel in settings reads the real tool list from the host; whatever you tick applies per agent:
37 tools, 34,271 chars → 28 tools, 21,224 chars
prompt 10,453 → 7,076 tokens (−32%, saved every turn)
Nothing is hidden by default, because what you hide is capability. The list has to be right: the host validates every tool name and rejects the whole set when one is unknown (the settings panel shows the raw error).
Session history is derived by the host from the log. The plugin appends one
surfaceOp: { op: 'replace', startSeq, endSeq } event, and the covered range stops entering
deriveMessages() — not a byte of the original log changes, and the tree still holds the full
text.
Default: fold past 40,000 tokens, keep the latest 3 turns, fold whole turns
Keep: fold past 60,000, keep 4 turns
Save: fold past 20,000, keep 2 turns, and hide 9 heavy rarely-used tools
Three presets sit at the top of the settings page, and every value is adjustable:
| Preset | Fold above | Turns kept | Tools hidden |
|---|---|---|---|
| Keep | 60,000 | 4 | none (closest to native behaviour) |
| Balanced (default) | 40,000 | 3 | none |
| Save | 20,000 | 2 | 9 heavy rarely-used tools |
| Setting | Default | Effect |
|---|---|---|
foldAboveTokens | 40000 | Fold past this; 0 turns it off |
foldKeepTurns | 3 | Keep this many recent turns verbatim |
foldScope | turns | turns folds whole turns, tools folds only tool output |
mandatoryContext | true | Retrieval always includes the answer a turn hangs under plus its question: measured dependency recall 43% → 99% |
fileRegion | auto | Retrieval returns the current text of files this session read: auto by budget, digest head only, content always full, off |
The placeholder left behind tells the model where the text went:
[folded] The previous turn was removed from the context to save tokens; the full text is kept in the conversation tree — call retrieve_context when you need the details.
Long answers are never summarised (a summary rewrites code and numbers), and are served by size:
<= 800 tokens the text as is
800-3000 verbatim excerpt: the head plus sentences matching the question
> 3000 one line saying what it is about, the line count, and a pointer to the tree
The long tier giving only a referent line is deliberate: code, numbers and exact wording must be read
from the tree with retrieve_context, and the hint says that an excerpt is not the original.
Everything is editable at runtime and stored in ~/.dsh/token-tree/settings.json (only keys you
changed); precedence is settings file > profile config.
| Key | Default | Effect |
|---|---|---|
autoInject | false | Push the whole retrieval block into the context every turn (about +428 tokens/turn) |
retrievalHint | true | Add one hint line only, about 57 tokens/turn |
hintAboveTokens | 12000 | Send the hint only once the conversation reaches this size |
autoReflect | true | At turn end, grade the failure, write a reflection, retry a better sibling branch |
admitRelevance | 0.3 | Retrieval admission threshold; relaxes once when it comes back empty |
toolDeny | [] | Tool names to hide (filled by the checklist) |
foldAboveTokens | 40000 | Fold threshold, 0 = off |
foldKeepTurns | 3 | Turns kept verbatim |
foldScope | turns | Fold scope |
tokenizerVersion | auto | auto / 3 / 4 / off (estimate + calibrate against the bill) |
locale | auto | Interface language: auto / zh / en |
API: GET /api/token-tree/settings returns { effective, overrides, path, availableTools, fold, toolRestriction, lastAssembly, … };
POST on the same path writes { key: value } (null clears an override);
POST /api/token-tree/preset writes a whole preset at once.
user/message ─┐
assistant/message ├─▶ TokenTreeService ─▶ MemoryTree (nodes / edge weights / current)
tool/result ─┘
│
Where does a new question attach?
├ a specific term (shared by ≤1/3 of nodes) + semantic similarity
│ → the answer that introduced that term
└ only generic words → a new branch under the root
user/message, assistant/message and tool/result; no
private events are appended.surfaceOp: replace; the log stays append-only.retrieve_context either.pnpm install
pnpm run build # TypeScript → dist/ + lib/client.js
pnpm test # 164 cases (140 backend + 24 browser)
pnpm run check # typecheck + tests
Zero-cost checks (no model needed):
| Command | Effect |
|---|---|
node scripts/bench-retrieval.mjs | Retrieval recall against token cost |
node scripts/probe-tree-of.mjs <session> | Replay one session's tree offline |
node scripts/probe-attach.mjs <session> | Attachment score for every decision |
node scripts/probe-fold-estimate.mjs <session> | How much folding would save |
node scripts/inspect-compaction.mjs | Count compaction events |
Scripts that need a model in the loop are scripts/ab-*.mjs and probe-*.mjs; their results live in
docs/experiments/.
The version in the repository is always a test version (x.y.z-test.N); the release script turns
it into a stable one:
powershell -File scripts/release.ps1 -DryRun # rehearsal
powershell -File scripts/release.ps1 # publish and move on to the next test version
It validates, sets x.y.z, publishes ./plugin with --tag latest, advances the repository to
x.y.(z+1)-test.0, then commits, tags and pushes. Any failure rolls back.
| Path | Contents |
|---|---|
src/core/ | Pure algorithms: graph, edge weights, path cost, weighted retrieval, grading and backtracking |
src/plugin/ | The DSH wiring: Config, the session service, tools, event subscriptions, HTTP routes, fold planning |
client/client.js | Browser half: dock, editor, graph view, recycle bin, rule bar, settings panel, preset picker |
tests/ | 164 cases, including client tests that mount real React under jsdom |
docs/experiment-context-cache.md | Every measurement (1–15) |
MIT © 2026 STRlantian