dsh-parallel-chat
在运行中的 DeepSeek Harness 代理旁运行隔离的只读并行对话。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-parallel-chat@0.1.0-beta.1Parallel Chat 以 dsh-parallel-chat 发布，当前版本为 0.1.0-beta.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
点击下方 Badge 复制 Markdown，粘贴到 README 即可。
验证 package.json 声明的 GitHub 仓库，即可管理这个公开页面。认领后，Hub 会优先安排当前版本的安全扫描，并在通过后公开展示结果。
认领这个 Plugin →中文 | English
Ask a private, read-only question about an active DeepSeek Harness task without interrupting the parent Agent.
Developer preview: Parallel Chat is being released as an npm prerelease. Its core chat flow works with the official DSH developer preview; native archived-session visibility still has a host limitation. See Compatibility.
From a DeepSeek Harness checkout:
pnpm dsh plugin --profile web add github:Glaz-j/dsh-parallel-chat
pnpm dsh web
Git dependencies run this package's prepare script. pnpm may pause the first install and show a codeload package key that must be allowed in the profile's pnpm-workspace.yaml. Add the exact key under allowBuilds, set it to true, and repeat the install.
Install the prerelease with the beta tag:
pnpm dsh plugin --profile web add dsh-parallel-chat@beta
pnpm dsh web
The beta tag makes the preview status explicit. npm is optional for DSH, but it provides a simpler and more reproducible installation than building a Git dependency.
Parallel Chat intentionally keeps the concise /sidechat command for invocation and compatibility.
Inspect the current snapshot without calling an LLM:
/sidechat
Ask a one-shot question:
/sidechat Why did the Agent choose this approach?
The parent composer unlocks immediately. Open the subagent list to watch the Parallel Chat run and read its answer.
Cancel the newest active Parallel Chat, or a specific request:
/sidechat cancel
/sidechat cancel 12ab34cd
Remove the plugin with:
pnpm dsh plugin --profile web remove dsh-parallel-chat
Parallel Chat receives two immutable inputs:
turn/end boundary./sidechat was invoked.The current-turn packet includes appended user messages, finalized assistant messages, and tool results. It excludes request headers, raw assistant chunks, command lifecycle events, runtime internals, and other non-visible records. The prompt packet is capped at 24,000 characters with deterministic middle truncation.
This is a capture-time snapshot. Parallel Chat does not continue following parent events after it starts.
recordInput: false).allow: []).agent.steer() or agent.followup() on the parent.Completed Parallel Chats remain in the plugin's retained set for 30 minutes. Each parent retains at most its five newest completed Parallel Chats; when a sixth settles, the oldest is archived immediately. Running children are never archived by the capacity rule.
Archival is non-destructive: the transcript stays persisted and the plugin no longer treats that child as retained. Startup reconciliation restores deadlines after a DSH restart. In official DSH 0.1.0-rc.7, an archived child may remain visible in the native subagent list; see Compatibility.
flowchart LR
U[/sidechat question/] --> C[DSH command registry]
D[Committed DSH session events] --> S[Snapshot service]
C --> S
S --> H[Stable history]
S --> O[Frozen current-turn observation]
H --> F[Native fork child Agent]
O --> F
F -->|child published| R[Immediate command receipt]
R --> P[Parent chat remains available]
F --> T[Native Parallel Chat transcript]
T --> W[DSH Web subagent UI]
T -->|settled| L[Retention and archive policy]
The command delegates through DSH's native fork subagent provider with a dedicated observer persona. DSH owns the Agent loop, child lineage, persistence, lifecycle events, and Web UI. The plugin owns snapshot construction, isolation policy, command receipts, cancellation, and retention scheduling.
The host-side snapshot API is:
const snapshot = ctx.sideChatSnapshots.capture(sessionId)
snapshot.events is the canonical closed prefix, snapshot.messages is the reconstructed model-visible surface, and snapshot.currentTurn contains capture metadata and filtered visible messages from the open turn.
^22.19.0 or >=240.1.0-rc.7 or a compatible developer-preview buildThe core command, snapshot, fork, isolation, cancellation, scheduling, and persistence paths use public DSH plugin seams and work with the official DSH developer preview.
DSH 0.1.0-rc.7 does not currently filter plugin-archived sessions from its native subagent list and count. Consequently, Parallel Chat's retention policy still runs, but an archived transcript may remain discoverable through the host UI. A host-side experiment exists in the project's development fork, but no upstream change is required or assumed for this prerelease. Treat 0.1.0-beta.1 as an integration preview while this presentation gap remains.
The bundle adds this default configuration:
- id: sidechat-observer
name: dsh-parallel-chat
config:
observeEvents: true
eventTypes: []
subagentProvider: fork
retentionMinutes: 30
maxRetainedPerParent: 5
| Option | Default | Meaning |
|---|---|---|
observeEvents | true | Emit metadata-only committed-event logs. |
eventTypes | [] | Exact event allowlist; empty observes all types. |
subagentProvider | fork | Context-inheriting provider with persona and tool-filter support. |
retentionMinutes | 30 | Minutes a completed Parallel Chat remains visible. |
maxRetainedPerParent | 5 | Completed Parallel Chats retained per direct parent. |
Set observeEvents: false to keep only lifecycle logs. Retention values must be positive integers.
pnpm install
pnpm run check
To load a local checkout:
pnpm dsh plugin --profile web add "C:\src\dsh-parallel-chat"
pnpm dsh web
Maintainers can run the real DSH loader smoke test by setting DSH_HARNESS_ROOT and running:
pnpm smoke:dsh
DeepSeek Harness currently discovers community plugins through the GitHub dsh-plugin topic rather than a curated registry submission form. Add the dsh-plugin topic to this repository so it appears alongside other community plugins.
DSH can install a plugin from GitHub, a local path, a tarball, or npm. Publishing to npm is therefore not required, but is recommended for stable releases because users receive a prebuilt, versioned artifact without Git install-time build approval.