dsh-side-chat-plugin
DeepSeek Harness 的 Codex 风格侧边聊天：当前会话在右侧边栏中的临时只读分支，关闭后即销毁。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:XBXyftx/dsh-side-chat#772dcdff9f8541ba02e3c61609f1518c7b0a5ea1Side Chat Plugin 以 dsh-side-chat-plugin 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
dsh-side-chat-plugin)中文 | English
A Codex-style side chat for DeepSeek Harness: open a temporary read-only branch of the current session in the right sidebar, ask "how is it going?" or "confirm that conclusion" while the main session keeps working, and destroy it by closing the tab.
It is related to, but not the same as, a fork:
sandbox/mode: read-only), with approvals pinned to never and a tool guard on mutating tools. It can query, never write.| Capability | Description |
|---|---|
| Sidebar entry | Adds a "Side chat" box to the right sidebar's guide page |
/btw | Opens the side chat from the composer |
| Shared context | Seed cut at the main session's latest completed turn |
| Read-only | Sandbox mode + approval policy + tool guard (three layers) |
| Progress | side_chat_progress reads events after the snapshot: user requests, assistant replies, tool calls, todo list |
| Report back | side_chat_report queues a result into the main session; can be disabled in settings |
| Close confirmation | "Close this side chat?" dialog with "Don't ask again"; cancel reopens the tab |
| Destruction | Disposes the agent and removes the session's JSONL directory; success is verified through the persistence seam |
dsh plugin add dsh-side-chat-plugin
Or from a local checkout while developing:
dsh plugin add /absolute/path/to/dsh-side-chat
Refresh the Web page afterwards; the plugin card appears in Settings → Plugins.
/btw in the composer.side_chat_progress.Right sidebar panel → "Side chat":
side_chat_report is refused and the side chat stays local.Plugin-row configuration (override the side-chat row in a profile or cordis.patch.yml):
| Field | Default | Meaning |
|---|---|---|
readOnly | true | Force the read-only sandbox in side chats |
allowReportToMain | true (volatile) | Whether reporting back is allowed |
progressEventLimit | 60 | Max events returned by one progress read |
preset | "" | Agent preset for side chats; empty inherits the main session's |
sessionsRoot | "" | Session storage root used for destruction; empty means $DSH_HOME/sessions |
src/) creates the hidden child with ctx.agents.create({ seed, inheritedEventCount, meta: { origin: 'subagent', parentSession, isSeeded: true }, setup }). The setup mounts the main session's preset, registers the read-only guard and the two tools, and appends sandbox/mode, approval/policy, subagent/descriptor.
subagent/descriptor is required: the Web client refuses ordinary history reads for an origin: 'subagent' session, and only a descriptor-backed child can use the subagent history route.client/client.js) contributes two tab types (draft page and addressed conversation), a resource provider that retains the session, a conversation.composer chain entry that replaces the composer, a shell.overlay close dialog, the /btw client command, and the settings panel.POST /side-chat/<endpoint> route on the web server (connection.requestRejection enforces the Host/Origin and browser-credential fence). Plain JSON, owner only.$DSH_HOME/sessions/<projectKey>/<sessionId>/). With another persistence backend or a custom root, set sessionsRoot; every removal is verified with sessionPersistence.stat() and a failure is reported honestly in the dialog./btw creates a fresh side chat and the old one is no longer reachable from the UI.0.2.1-rc.2 (commit 687f282e).sandbox/mode: read-only guarantees writes fail; bash may still run read-only commands.webServer and connection, so it targets the Web/desktop deployments; a headless profile without a web server leaves the Host half inactive.npm install
npm run typecheck
npm test
npm run build # emits lib/ for `dsh plugin add`
MIT © 2026 XBXyftx