dsh-attach

Attach a terminal UI to a running DeepSeek Harness host. The Host plugin exposes sessionController over a local socket or named pipe; the client sees the same sessions, turns, approvals, and questions as the Web UI.

Host process  ◀── local socket / named pipe ──▶  dsh-attach
sessionController                               terminal UI

No second harness, TCP port, account, or login. The bridge is local-only and uses a per-process token.

Quick start

Requirements: a running DSH Desktop or Web host, the same OS user, and Node.js ^22.19.0 || >=24.0.0.

dsh plugin --profile desktop add ./dsh-attach
dsh-attach --list
dsh-attach

Windows: run from Windows Terminal/ConPTY and use: %USERPROFILE%\.dsh\profiles\desktop\node_modules\.bin\dsh-attach.cmd.

The first install must be loaded by DSH. Later upgrades can apply through Plugin Manager/profile recomposition or HMR without a full app restart.

See Getting started for install and CLI details.

Features

• Sessions: list, resume, create, fork, archive/unarchive, pin/unpin, presets.
• Live view: streaming text/reasoning/tools, turn folding, timestamps, activity labels, token/context/permission status.
• Interaction: approvals, questions, goals, plan mode, todo list, queue.
• Search and history: /find, Ctrl+R//history, durable older pages.
• Subagents: lineage, read-only history, continue/interrupt, parent navigation.
• Commands: / completion for local/Host commands and arguments; Host command passthrough.
• Side questions: /btw overlay; f forks with full tool access.
• Detail levels: Ctrl+G or /detail compact|standard|verbose.
• Jobs and Herdr: background-job output; Herdr state, titles, preview panes.
• Reconnect: automatic retry after Host restart, /reconnect on demand.
• Cross-platform: Unix socket or Windows named pipe; Windows TUI requires a ConPTY terminal.

Documentation

Guide	Contents
Getting started	Requirements, install, CLI, upgrade
Usage	Sessions, prompts, approvals, subagents, jobs
Keys and commands	Keyboard and slash-command reference
Configuration	Host options, env vars, themes
Herdr	Agent status and preview panes
Diagnostics	Logs, exit reasons, performance
Security	Trust boundary and transport
Troubleshooting	Common failures
Development	Architecture, protocol, tests, release

Security

• Local-only transport: Unix socket or Windows named pipe. No TCP listener.
• Timing-safe 32-byte token authentication.
• Unix socket/descriptor use owner-only permissions; Windows relies on ACLs plus the token.
• Rendered Host/model output is sanitized for terminal control sequences.
• Anyone who can connect can operate that Harness.

See Security.

Limitations

• Clipboard-only image input; no @ file indexing or file upload.
• One session per terminal; other sessions keep running.
• Subagent history is read-only; control is limited to follow-up messages and interrupt.
• Herdr integration is Unix-only.
• Loaded history defaults to 300 messages; paging reads further back.

License

MIT. See LICENSE.