@freepeak/dsh-mux
DeepSeek Harness 插件：从图形界面与编程 CLI（Claude Code、Cursor、……）对话，并保持对话线程。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:FreePeak/dsh-mux#5c13e253042bbe3b65e0052e5e93bdacb4e3f54c
Mux 以 @freepeak/dsh-mux 发布，当前版本为 0.2.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Talk to other coding CLIs from inside the DeepSeek Harness GUI — and keep the thread.
Install · CLIs · Architecture · Docker · Dev · License
dsh-mux is a DeepSeek Harness external bundle: a sidebar page, slash commands, a host tool, and a remote service that let you talk to other coding CLIs — Claude Code, OMP, Pi, Cursor, Agy, Command Code, opencode — from the DSH web GUI, with each conversation kept alive as a thread.
Instead of switching terminals, open Mux, pick a CLI, type a follow-up, and the same CLI session continues where it left off (resume by the CLI's own session id). Stream output in real time, stop a turn in progress, or hand a session id to the model with the mux tool.
This is not a standalone server, not a HarnessRouter deployment, and not a live bidirectional PTY. It runs one CLI process per turn, resumed by session id.
Mux panel with discovery strip
# from a clone or release checkout
dsh plugin install /path/to/dsh-mux
Installed into the active web profile (patch reload is live on that profile, so later edits to the bundle are picked up without a full restart).
Put the target CLI binaries (
claude,omp,pi,cursor,agy,command-code) on yourPATH.opencodeis tracked but reported as missing until its binary appears.
| Node.js | ≥ 22 (build + tests) |
| Host | DeepSeek Harness web profile (dsh web) |
| Optional | Playwright (container drive script) |
dsh web prints http://127.0.0.1:3081/?token=...).From the composer:
/mux # open the Mux panel
/mux claude say hi # start a thread; result goes to the transcript
/ask omp explain this # same thing, shorter name
A self-contained container boots DSH with dsh-mux installed, including a
fixture claude CLI (docker/fixtures/claude) that validates the full
spawn → stdin → session-id → resume pipeline without model credentials:
docker compose -f docker/docker-compose.yml up --build -d
docker compose -f docker/docker-compose.yml logs -f # `dsh web:` line has the token
Open http://127.0.0.1:3101/?token=... (host loopback only — the harness
refuses a wildcard bind, so an in-container relay forwards to its private
127.0.0.1:3099).
| Re-seed profile | FORCE_REINIT=1 docker compose -f docker/docker-compose.yml up -d |
| Full reset | docker compose -f docker/docker-compose.yml down -v |
scripts/drive.py walks the container end-to-end over the
harness wire API (workspace → session → commands.execute → panel) and
captures:
| Screenshot | Proves |
|---|---|
| 01 · boot / sidebar | Container boots; client bundle loads; Mux entry renders |
| 02 · commands | /mux + /ask claude execute; fixture returns mux · claude · exit 0 |
| 03 · discovery | Panel + discovery strip via remote.mux.discover() |
| 04 · thread turns | Stored thread shows prompt / answer turns |
Full transcript (including the resume proof — a second send on the same
thread passes cliSessionId to --resume and the fixture echoes it back):
docs/screenshots/drive.log.
python3 scripts/drive.py "http://127.0.0.1:3101/?token=..." # needs Playwright
python3 scripts/shot.py "http://127.0.0.1:3101/?token=..." # onboarding walkthrough
Every adapter keeps the prompt on stdin, never in argv, and runs in non-interactive accept mode so a turn can never block on a prompt nobody can see.
| CLI | First turn | Resume turn | Status |
|---|---|---|---|
| Claude Code | -p --output-format stream-json | --resume <id> -p | ready |
| OMP | -p --mode json | --resume <id> -p | ready |
| Pi | -p --mode json | --resume <id> -p | ready |
| Cursor | agent -p --output-format stream-json | agent --resume <id> -p | ready |
| Agy | -p --output-format stream-json | --conversation <id> -p | ready |
| Command Code | -p --output-format json --skip-onboarding | --resume <id> -p | ready |
| opencode | (binary missing) | (n/a) | missing |
You ──► DSH Web GUI
│
┌──────┴──────────┐
▼ ▼
Mux page DSH agent
(thread list, (/mux, /ask,
composer, tool mux)
Send / Stop)
│ │
└────────┬─────────┘
▼
dsh-mux host ──► Thread store (cliSessionId)
│
▼
Coding CLIs (one process per turn)
Interactive diagrams:
{ tool, prompt, threadId }
so an agent can start or continue a thread inside a larger task.ctx.remote.$mount) and reads via ctx.get('remote.mux').runTurn spawns the chosen CLI with print args + permission-mode flag.mux · claude · 4.2s · exit 0.Default ceilings: 10 minutes per turn, 1 MiB combined output.
Host config (schemastery) — all fields are .default(...) (no .optional()):
| Key | Default | Meaning |
|---|---|---|
| turn timeout | 600000 ms | Wall clock per spawn |
| output cap | 1048576 bytes | Combined stdout + stderr |
| (empty string fields) | '' | Reserved / path overrides |
See src/plugin.ts for the live schema.
npm install
npm test # 28 tests, offline
npm run build # tsdown → lib/*.mjs
| Script | Purpose |
|---|---|
test | node --experimental-strip-types --test test/*.test.ts |
build | Bundle src/index.ts + src/remote.ts into lib/ |
Every push and pull request to main runs .github/workflows/ci.yml:
npm ci → unit tests → build → artifact gates. While the repository is
private, jobs run on a self-hosted macOS runner labelled dsh-mux
(~/actions-runners/dsh-mux, launchd service) so they do not burn the org's
limited hosted Actions minutes. If the repository is made public, switch
runs-on back to ubuntu-latest before opening it — fork PR code must
never execute on a maintainer machine.
dsh-mux/
├── assets/ # logo, mark, favicon, social card
├── package.json # dsh.bundle + dsh.client, exports (./, ./remote, ./client)
├── cordis.patch.yml # rows: dsh-mux + dsh-mux-remote
├── client.js # browser: sidebar + panel + remote contribution
├── docker/ # Dockerfile, compose, entrypoint, fixture claude
├── scripts/drive.py # container validation + screenshots
├── src/
│ ├── adapters.ts # seven CLI specs
│ ├── discovery.ts # PATH strip
│ ├── run.ts # spawn / stream / cap / kill
│ ├── threads.ts # JSON thread store
│ ├── commands.ts # /mux + /ask parser
│ ├── plugin.ts # host tool + commands (no default export)
│ ├── remote.ts # host remote (hand-applied @Remote markers)
│ └── index.ts # cordis entry (named exports only)
├── test/ # 28 tests + artifacts gates
└── docs/ # PRD, diagrams, screenshots, UI sketch
Hard-won constraints (also in CONTRIBUTING.md):
export default (inject would be stripped).@Remote in shipped JS — hand-apply markers..default(), not .optional().ctx.get('remote.mux'), not ctx.remote.mux.| Asset | |
|---|---|
| mark | mark.svg · favicon.svg |
| logo.svg · logo-dark.svg | |
| mark-light.svg · mark-mono.svg | |
| social-card.svg (1280×640) |
Two inbound strokes join at a mux node and leave as one outbound trunk with a green continuity dot — many CLIs in, one resumed thread out. Details: assets/README.md.
Spawning local CLIs is intentional and constrained: prompt on stdin (never argv), fail-closed turns, real time/output ceilings. See SECURITY.md for the supported versions line and how to report vulnerabilities privately.
Contributions are welcome. Please open an issue before large changes. Read CONTRIBUTING.md and the Code of Conduct.
PR checklist (short form):
npm test green (28)npm run build if host/remote sources changedCHANGELOG.md updated when behaviour changesSee CHANGELOG.md.
MIT © FreePeak
Built for the DeepSeek Harness ecosystem. Not affiliated with Anthropic, OpenAI, Cursor, or any of the supported CLIs.