dsh-side-branch
DSH 侧枝会话：从主会话派生一条只读分支，每轮追问都用主会话最新的已结算内容重建上下文以继续命中前缀缓存，答案不进入主会话的模型上下文。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:wucl12/dsh-side-branch#c6c700fbc6a0b4ed56b962af67606f96d35fa18aSide Branch 以 dsh-side-branch 发布，当前版本为 0.2.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 简体中文
Select text in the main session, and a read-only branch session will pop up in the right sidebar. It inherits the existing context of the main session, streams its answers token-by-token, and its responses never pollute the model context of the main session.
Core Scenario: Asking follow-up questions, looking up terms, or exploring ideas based on the current conversation without interrupting the flow of the main session.
dsh-side-branchpnpm installed in the local PATH.0.1.5-rc.2 and 0.1.7-rc.2The Side Ask entry in the right sidebar guide
Before developing this project (Sep 2026), I surveyed 14 side-chat/bubble plugins in the DSH ecosystem and found that none of them could simultaneously meet all the following hard requirements:
The closest alternatives all had compromises: @michengai/dsh-btw was one-off and lacked streaming; dsh-side-chat-plus didn't inherit history by default; dsh-sidenote was feature-rich but extremely heavy (requiring a 14.7 MB dependency); @lukeknow0/dsh-side-chat had excellent architecture but was unmaintained.
The biggest divergence lies in how "read-only" is implemented: similar plugins universally use toolFilter to forcefully remove tools from the prompt. However, this causes the branch's prompt prefix to diverge from the main session, rendering the parent session's accumulated prefix cache completely invalid.
This project strictly chooses to enforce read-only at the execution layer. Thus, the branch's prompt prefix remains byte-identical to the main session, continuing to enjoy an extremely high prefix cache hit rate (empirically 97%–98%).
ctx.tools.guard whitelists only six query tools without side effects (read, glob, grep, web_search, web_fetch, lsp). Other instructions (like writing files or executing scripts) are directly rejected at the execution layer.After installation, you must restart DSH for the client plugin to load properly.
Install via npm (Recommended):
dsh plugin --profile web add dsh-side-branch
Install via GitHub:
dsh plugin --profile web add github:wucl12/dsh-side-branch
🤖 Prompt for AI Agents: If you are an Agent responsible for installing this plugin or reading its source code, please prioritize reading
AGENTS.mdin this repository for hard constraints, architectural details, and automated installation guides.
↗ on the right side of the main session's input box. Click it to directly summon the Side Ask panel (can be disabled in settings).web_fetch / web_search still have network access, and read can read files within the process's permissions. The allowlist is hardcoded and cannot be relaxed via settings.turn/end) — but manual selection quoting is not affected by that: the limitation is on "seeing it automatically", not on "being able to quote it".DSH_HOME and run at the same time, that sweep skips entirely — a second DSH never has its live branches deleted.contextFull.used is an estimate (a rebuilt session has no usage yet), so it will not match the real usage once a turn settles.ptc preset (pure code execution tool surface), since run_code is permanently rejected by this plugin, the branch will fall back to a pure text Q&A mode (no tools can be called).docs/TECHNICAL.md: full technical reference — prefix-cache mechanics, the read-only enforcement pipeline, PTC behaviour, and every known limitation.AGENTS.md: Architectural contracts and hard constraints strictly written for AI Agents.SECURITY.md: Security commitment scope and vulnerability reporting channels.docs/CHANGELOG.md: Version release history.