dsh-sidecar-conversation
原生 DeepSeek Harness 侧边栏中的会话绑定聊天
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-sidecar-conversation@0.2.9Sidecar Conversation 以 dsh-sidecar-conversation 发布，当前版本为 0.2.9。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Don't understand part of an AI answer? Ask beside it, without cluttering your main Session's context.
In DeepSeek Harness Web, select unfamiliar text and ask for an explanation in the native right sidebar. Follow-up questions and explanations stay in their own Session, without being written back into your main conversation. You can also ask about a whole turn or fork from an earlier point, with separate messages, drafts, model and permissions.
简体中文 · GitHub Release · npm
With DSH Web already installed, run this command in the same environment and DSH_HOME you use to start it:
dsh plugin --profile web add dsh-sidecar-conversation@0.2.8
Restart DSH Web and refresh the page. Keep your existing DSH_HOME to preserve conversations and Sidecar history. No DSH source changes or Better Sidebar installation are needed. Version 0.2.8 has been verified in an isolated, unmodified DSH 0.2.1-rc.3 host.
Select text in a completed answer, or click “侧问这个回合”, then choose Fork or a references-only conversation and ask on the right.
The full native session list is now the default. Its rows, workspace management, search, pinning and archiving remain owned by DSH. Use the footer toggle for the optional collapsible Sidecar view; an explicitly saved choice is preserved.
Unsent sidecars no longer occupy reusable workspace blanks. Ordinary New Session therefore keeps native permission defaults instead of inheriting an old sidecar's settings and showing Custom. First-turn attachment and legacy blank recovery preserve native logs and permissions.
Implementation boundaries and verification
Watch: ask about unfamiliar text without cluttering the main Session's context
Watch on Bilibili: real multi-turn conversations in an isolated environment, showing Fork, references-only Sessions, appended references, precise source navigation, native composer controls and history recovery. The full page stays visible, with red circles marking the focus. Waiting is edited out; some operations are sped up, with AI voice narration.
The right-hand chat uses DSH's native composer: file uploads, model and reasoning selection, permission controls, messages, tool calls, approvals, stop and error displays. A Sidecar supports continued conversation across multiple turns.
Select text in a completed Assistant answer, or click “侧问这个回合” at the end of a turn, to open the action menu.
| Menu action | Text selection | Whole turn |
|---|---|---|
| 追加到最近侧问 (append) | Add the selected text to the target draft | Add a whole-turn reference to the target draft |
| 从此回合 Fork | Inherit history through the selection's turn and attach its text reference | Inherit history through the turn and attach its turn reference |
| 仅用选文新建／仅用此回合新建 (independent) | Start with only the selected text | Start with only that turn's final Assistant answer |
Append appears only when the current main Session has a prepared Sidecar whose tab remains open. Both menus have two creation choices, optionally preceded by append. The text-selection menu ends with “添加到主会话” (add to main Session), which inserts the same clickable reference into the native main composer without creating or switching a Sidecar. Drafts and sent citations retain exact-selection highlighting. If the right dock is collapsed but the tab remains open, append reveals the target Sidecar. Closed tabs and unprepared drafts are not eligible targets.
The left menu determines the creation mode. Choosing a new chat prepares its Session and opens the native composer directly, without another mode choice or an automatic model call. The new draft contains only the current source and does not copy another Sidecar's selections.
Selections are limited to 4,000 characters. A whole-turn reference points to the final Assistant answer; independent Sessions receive that explicit reference, while only Fork inherits earlier history. Missing or unreadable sources produce an error while preserving the reference.
| Linked Sidecar (Fork) | Independent Session | |
|---|---|---|
| Context | Main conversation history through the selected turn | Only explicitly added references and questions |
| Native relationship | Child of the main Session | No native parent, alongside the main Session |
| Fork progress | Links the fork turn, lag count and latest parent turn | Indicates references only, without a Fork gap |
| History entry | Listed in the source Session's Sidecar history | Also recoverable from the source Session's Sidecar history |
A Fork contains context from the point of branching and does not follow the main conversation live. The progress row updates when the main Session adds turns; appending references neither reduces the lag count nor merges later history automatically.
Both modes use the source workspace. Menu-created chats use DSH’s native read-only preset and permission menu. The inherit permission option copies the main Session’s current preset once; later permission changes are independent. Genuine custom permissions retain their native sandbox and approval values. Tools with write access modify the same workspace files. Read-only does not imply network isolation. Sidecar messages belong to their own Session and are not automatically sent back to the main conversation.
Initial titles summarize the first question. The left list, right tab and history then read the native Session title, including manual renames. Linked Sidecars use the native row's leading ↳ decoration and hover card; native activity indicators take precedence. History follows native manual order, recency, pins and workspace grouping through a plugin-owned read-only adapter over the existing Workspace view store. Folding groups does not hide their history entries.
Sidecar history supports creation, reopening, archival and restoration. Closing a tab closes its view without stopping background generation; plugin archival does not delete the native Session. History creation starts from the main Session's latest completed answer and offers Fork or independent mode; without a completed answer, it asks you to finish a turn first.
Messages, replies, attachments and tool events use native DSH Session capabilities. sidecar-conversation.json stores the Sidecar index; drafts and tab layouts are browser state. After clearing browser data, history can reopen sent conversations, but session logs cannot recover unsent drafts. Native session-log ownership and upgrade boundaries
Version 0.2.8 uses public DSH APIs and its unified list was verified against unmodified DSH 0.2.1-rc.3. No DSH source patch or Better Sidebar installation is required:
sidebar.session.row.leading / sidebar.session.row.hover: existing public row decorations; titles remain native.sidebar.workspaces / shell.overlay: the public slot ledger supplies the existing root view-store handle; the plugin renders the unified list and reuses native preferences and ordering actions, without a second order store.All Sidecar extensions live in the plugin; no DSH source patch or custom uiWorkspace.sessionOrder / sidebar.workspaces.session.title service is needed. A public sidebar slot supplies a collapsible Session tree from the plugin registry, including on rc.3 where ordinary Fork logs omit parent links. Independent chats remain roots. Native titles, order data, composer and session logs remain authoritative. The full native list is the default: DSH owns row rendering, search, ordering, pinning, archiving and workspace management. A persistent footer toggle opens the plugin's collapsible hierarchy view. That optional view uses native state and actions but still renders its own rows; it needs compatibility testing when DSH changes. No private row imports or DSH patches are used.
Unsent independent sidecars keep their native Session and logs outside workspace membership until their first native turn starts. This prevents native New Session from reusing a reserved blank with sidecar permissions. Recovery also detaches legacy blank sidecars without rewriting permissions or deleting logs; they remain accessible through sidecar history. Ordinary new sessions retain DSH's native defaults.
To develop from source, install a locally built plugin through a DSH Web profile:
pnpm install --frozen-lockfile
pnpm check
pnpm test
pnpm build
dsh plugin --profile web add link:$(pwd)
dsh --profile web --dump-config
Restart the target Web instance after installation. --dump-config proves composition only; open the page to verify runtime loading. Use a separate DSH_HOME, port and plugin directory for development builds to protect your daily instance. Uninstall with dsh plugin --profile web remove dsh-sidecar-conversation. Development and verification
The plugin passes 176 tests and TypeScript checks; its release tarball passed an independent build, entry checks, clean installation and Host-entry import. Browser and real-model coverage are recorded separately below:
These results do not imply that every DSH Web check passes; the linked records describe known baseline failures and remaining coverage gaps.