dsh-sidechain: A Side-Conversation Plugin for DeepSeek Harness with /btw and /side
buyi-wsgzg/dsh-sidechain
A DSH plugin for side conversations, running /side and /btw in forked sub-sessions without touching the main thread.
Create independent sub-sessions in DeepSeek Harness via forking, enabling one-off questions or ongoing conversations without affecting the main session history.
dsh plugin --profile web add github:buyi-wsgzg/dsh-sidechain- Category
- Sessions & Messages
- Platform
- DSH-Plugin
- Author
- buyi-wsgzg
- Distribution
- Plugin
dsh-sidechain Key Features
dsh-sidechain Repository
dsh-sidechain Repo Summary
dsh-sidechain is a side-conversation plugin (DSH plugin) for DeepSeek Harness, maintained by omdsh-dev under the BSD-3-Clause license, last updated in 2026-08. It forks the current session to create independent sub-sessions, allowing users to ask one-off questions or hold ongoing conversations without interrupting the main thread, solving the problem of polluting the main session history with temporary queries. Core capabilities include /btw one-off side questions, /side persistent side sessions, an embedded right-side chain panel, session isolation, and persistence.
What core commands does the dsh-sidechain DSH plugin support?
The plugin provides three commands: /btw <question> initiates a one-off side question, ideal for quick confirmations, runs only once and is read-only; /side <question> creates a persistent side session that can be continued in the side panel; /side list lists direct sub-agents of the current session. All commands require a question; /btw and /side run in the background, allowing the main session to continue.
How to install and configure dsh-sidechain?
Use the following installation command. It depends on DSH's dsh-subagent, dsh-subagent-fork, and dsh-commands plugins, which are included by default in the Web profile.
dsh plugin --profile web add github:buyi-wsgzg/dsh-sidechain
On pnpm 10 and above, the first install prompts to allow Git dependencies to run prepare; follow the output to add the plugin key to the Web profile's pnpm-workspace.yaml and re-run the install. The plugin adds a config layer to the profile, allowing you to set providerName (default fork), persona (side-session behavior constraints), and readOnlyTools (tool allow-list). After installing or updating, restart dsh web and refresh the page.
How to use the side-chain panel of dsh-sidechain?
The side-chain button in the session title bar opens the right panel, listing direct sub-agents of the current session with type, title, running status, and activity summary. Selecting a thread shows the full timeline: user messages, model answers, context injection, thoughts, tool calls and errors, with support for Markdown, code blocks, tables, and formulas. /side threads have an input box for continued conversation; /btw threads are read-only. The panel supports drag-to-resize, expand, manual refresh, and a Ctrl/Cmd+Shift+E shortcut toggle.
How does dsh-sidechain ensure session isolation?
The fork inherits only completed turns from the parent session, used as reference; messages after the boundary are the side session's current task. Each side session has an independent log; messages, tool activities, and answers do not enter the main session's model context. The main session only retains the command result that created the side session. The default persona allows non-destructive exploration, not actively modifying files, requesting privilege escalation, or creating sub-agents; actual permissions are determined by DSH's sandbox and tool configuration.
What are the limitations and development methods of dsh-sidechain?
Limitations include: the fork does not include in-progress turns of the parent session; /btw runs only one round; /side list lists all direct sub-agents, not limited to those created by this plugin; /side must include an initial question, as the current subagent API does not support empty threads waiting for first input. For development, run pnpm install and pnpm check; dependencies are pinned to public DSH rc.5, no local DSH source checkout needed.