@local/dsh-btw-sidechat
DeepSeek Harness 的顺带侧边聊天：当前对话的只读分支，在 Codex 风格的右侧边栏窗口中回答。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:Big-Smarty/dsh-btw-sidechat#99d099698fd6dc4b6254a5795c77eba35e4ebec6Btw Sidechat 以 @local/dsh-btw-sidechat 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Ask a side question in DeepSeek Harness without interrupting the main task. /btw forks the current conversation with its full context, answers in a read-only side chat, and opens the answer in a Codex-style right-sidebar window.
/btw forks the latest completed-turn prefix of the current conversation. The child sees the parent's user messages, assistant answers, and tool results — no re-summarization step.read, read_image, glob, grep, web_search, web_fetch, and skill. A monotonic per-agent guard denies every other tool, including run_code and any tool registered later. Deployments that register a tool on the agent scope (some delegation tools do) may still show that tool's schema; the guard denies its execution.dsh-resource://btwchat/... tab opens in the right sidebar with the normal Conversation: the inherited transcript, streaming answer, Markdown, and a composer for follow-ups.Requires DeepSeek Harness 0.2.1-rc.2 or a nearby version with the right sidebar, the Session Controller, and /btw command support.
Open Plugins in the DSH sidebar.
Choose Add plugin → Install third-party plugin.
Enter the repository URL:
https://github.com/Big-Smarty/dsh-btw-sidechat.git
A local clone path works too and keeps the checkout linked for edits.
Install and enable the bundle, then refresh the page once so the client half loads.
Or ask a DSH agent to install the bundle from the same URL.
git clone https://github.com/Big-Smarty/dsh-btw-sidechat.git
cd dsh-btw-sidechat
npm test
Install the cloned directory through Plugins → Add plugin as above.
Only one plugin may provide the global
/btwcommand. Disable any other/btwplugin (for example@michengai/dsh-btw) before enabling this one; two global commands with the same name are a load error, not a shadow.
| Action | How |
|---|---|
| Ask a side question | /btw why does the retry test fail? |
| Read the answer | The side chat opens automatically in the right sidebar |
| Follow up | Type in the side chat's composer; the same read-only child answers |
| Reopen | Click Open on the /btw card in the parent transcript |
| Close | Close the tab; the child session stays in the session list |
The side chat is a normal forked session, so it also appears in the workspace's session list and survives a restart. Its read-only policy is re-installed when it is resumed.
The fork is cut at the latest completed turn. A /btw sent while the parent is mid-turn does not include the in-flight turn; a conversation with no completed turn returns a helpful error instead of creating an empty child.
The side chat cannot write files, run shell commands, edit code, change configuration, create goals or schedules, spawn subagents or workflows, ask blocking questions, or read other sessions. It can read workspace content and the web. Its own conversation is a separate fork, so follow-up prompts and answers never enter the parent context.
sessionController.fork({ sessionId }), which creates a forked child with the parent's event prefix and preset.tools.schemas(child), installs tools.restrict and a tools.guard, and adds a btw:side-chat system-prompt section.BTW · <question>, which is also the durable marker used to re-adopt the policy after a cold resume.sessionController.prompt, then returns a dsh-resource://btwchat/session/<child>?parent=…&q=… address in the command result.btwchat resource provider, a right-sidebar tab type and body, a command card keyed btw, and a local command/executed listener. The listener refreshes the session catalog, then opens the tab.conversation.content factory in embedded mode inside the child's SessionProvider. The inherited transcript and composer are the shipped ones.More detail: docs/ARCHITECTURE.md.
command/executed is local. Auto-open happens in the browser tab that submitted /btw. In another tab, after a reload, or after a Host-side invocation, use the command card's Open button.BTW · prefix; the live process keeps the restriction, but a later cold resume of that renamed session will no longer recognize it as a side chat.tools.restrict filters inherited tools; a tool registered directly on the child's agent scope (for example a delegation tool added by a preset) stays in the schema list. The guard denies its execution, and the side-chat prompt states that only the listed tools are available.web_search and web_fetch can send text to search providers. If the inherited transcript is sensitive, remove them from READ_ONLY_TOOLS in index.js.npm test
The tests use Node's built-in test runner and cover command parsing, title and address codecs, the read-only intersection, policy text, the fork/adopt/prompt flow, error mapping, root-versus-child tool presentation, resume adoption, and the client module shape. CI runs on every push and pull request.
A live Host probe on 2026-10-20 forked a small fixture session, prompted the child with /btw Reply with exactly: BTW PROBE OK, and observed:
BTW · Reply with exactly: BTW PROBE OK;BTW PROBE OK;btw:side-chat section in the child's assembled prompt;read, glob, grep, skill, read_image, web_search, and web_fetch visible;bash, write, edit, and run_code absent (a preset-scoped subagent schema remained visible but is guard-denied);The live Client slot tree confirmed the right-sidebar tab body, the btw.conversation child slot, and the btw command card. The auto-open path is client-local; it was verified by registration and codec tests rather than by driving the browser.
index.js Host half: /btw command, fork, read-only policy, resume adoption
client.js Client half: resource provider, sidebar tab, command card, auto-open
cordis.patch.yml Loads the bundle row
locale/ Plugin-inventory metadata (en, zh)
test/ Node tests for the pure helpers and the Host flow
docs/ Architecture and design notes
The btw prompt is adapted from oh-my-pi's /btw side question (Ephemeral side question for current interactive session. Answer briefly, directly; use conversation context already provided. NEVER use tools. NEVER ask follow-up questions.). This plugin keeps the direct-answer discipline but changes two premises: DSH has a durable, forkable session log, and the user asked for a read-only side chat with its own tools. The result is a read-only tool surface and a side window instead of a one-shot overlay.
A side chat makes one additional model request series over the inherited prefix, then one per follow-up. The plugin runs Host code in-process with your permissions; install it only if you trust the source. It cannot widen the parent's permissions and does not bypass approvals, sandbox policy, plan mode, or workspace restrictions.
MIT. See LICENSE.