Preface¶
In DSH, the main conversation often already carries a longer task chain. If you temporarily need to perform parallel verification, split problems, or let another agent run a round first, stuffing all those processes back into the main conversation will make its context longer and messier.
The DSH Side Chat plugin provides a parallel side conversation: the side conversation has its own independent context window, and when finished, a summary is brought back to the main conversation without polluting its context.
It is maintained by 2031814001yuyue-tech and is licensed under MIT. It targets DSH users and agent developers, solving the problem of “parallel branch conversations not polluting the main thread.” The DSH ecosystem emphasizes “everything is a plugin”; the community directory is an independent site and has no official affiliation with DeepSeek / High-Flyer.
What This Is¶
DSH Side Chat is a DSH plugin that allows you to open a real parallel agent session outside the main conversation.
The side conversation has its own independent context window with context isolation. The side panel lists all side conversations, and you can click to switch between them. When finished, the side agent can summarize itself and bring the summary back to the main conversation as a single-line collapsed snippet.
Core Features¶
Below are the verified plugin capabilities:
- Real parallel agent sessions
- Independent context window
- Context isolation
- Side panel lists all side conversations, click to switch
- Summary brought back to main conversation
- Clean conversation flow
- Message Markdown rendering
- Adjustable panel width (300–900px)
- Minimizable
- Smart auto-scrolling
- Zero pollution in conversation list
/sidecommand
Among these, “zero pollution in conversation list” means side conversations do not appear in the regular conversation list; the panel is the primary entry point.
Installation and Activation¶
The plugin supports two loading methods: the dynamic Cordis plugin method is suitable for development and debugging, while the npm package method is suitable for daily use. Both can coexist.
Dynamic Cordis Plugin Method¶
This method loads through DSH’s dynamic Cordis plugin flow, with zero dependencies and immediate effect upon change.
- Open the dynamic plugin definition interface in DSH.
- Create a new plugin, and paste the contents of
src/host.jsandsrc/client.jsrespectively. - Run the plugin and approve the Client half-authorization.
- After refreshing the page, a side panel entry appears on the right side of the conversation title bar.
npm Package Method¶
This method persists across restarts and is suitable for formal use.
First, install the package:
npm install dsh-side-chat
Then, in the target profile’s package.json, add dsh-side-chat to dsh.profile.bundles. For example:
"dsh": {
"profile": {
"bundles": ["dsh-side-chat"]
}
}
Note: Do not manually add a loading line to the target profile’s cordis.patch.yml to avoid duplicate registration. It takes effect after restarting DSH.
The npm method declares peerDependencies, requiring:
"react": "^18.2.0"
Typical Usage¶
Below are the common operations from opening the panel to bringing back conclusions.
- Click the side panel entry on the right side of the conversation title bar to open the panel; select “New” to create a side conversation.
- Send a message in the panel input box; press
Enterto send. The status dot indicates the current side conversation state: gray for idle, lit for running, red for error. - When needed, select “Bring back to main conversation.” The side agent automatically summarizes, and the summary is injected into the main conversation as a one-line collapsed snippet.
- After selecting “Minimize,” the panel collapses into a pill in the bottom-right corner, and the side conversation continues running in the background; click the pill or the sidebar button to restore.
- Drag the left edge of the panel to adjust its width, ranging from 300 to 900px; double-click the left edge to reset to 380px.
- Selecting “Close” stops the side agent. The conversation data remains on disk but is archived and does not appear in the list.
- You can also directly use the command to create and send the first message:
/side Look up xxx
Each main conversation supports up to 8 concurrent side conversations.
Applicable Scenarios and Notes¶
This plugin is suitable for the following scenarios:
- Wanting to process an independent question in parallel while the main task is ongoing.
- Wanting to move branch discussions or temporary reasoning into an independent context to avoid lengthening the main conversation.
- Wanting the side results to eventually enter the main conversation as a summary rather than flooding the main conversation with the full process.
- Needing interactions like the side panel, Markdown rendering, and background minimization.
Notes before use:
- The plugin runs with the current DSH process permissions. Before installation, you should inspect source code such as
src/host.jsandsrc/client.js, and confirm whether the MIT license meets your usage requirements. - The side conversation registry is in-memory; after a DSH restart, side conversation data remains in the session directory on disk but will not reappear in the conversation list.
- The visibility of
/sidein the Web input box depends on how the current DSH version exposes custom commands; the panel button is available in all versions. - When the main conversation is busy, “Bring back to main conversation” will prompt you to retry later and will not interrupt the ongoing main conversation.
Conclusion¶
The value of DSH Side Chat lies in separating parallel branch conversations from the main conversation context while retaining the closed loop of “summary bring-back.” It is suitable for DSH users as a daily plugin and for developers as a reference for the two loading methods: “dynamic Cordis plugin + npm package.”
Verified materials did not provide a confirmable catalog page URL. GitHub address:
https://github.com/2031814001yuyue-tech/dsh-side-chat