dsh-plugin-terminal-panel

dsh-plugin-terminal-panel

English | 中文

Real terminals inside the DeepSeek Harness web UI. One click in the sidebar adds a terminal panel beside the Conversation panel. Each tab is a real PTY (node-pty / ConPTY) — not a fake output box, and no OS window.

• The PTY lives in the DSH host process; output is streamed to the page over SSE;
• Closing or reloading the page does not kill anything: terminals keep running and replay the last 256 K characters, so the screen comes back;
• The PTY is resized with the panel, so full-screen programs redraw correctly;
• The same terminals are exposed to the agent as a tool set: the model can open a terminal, run commands and read the output.

✨ Features

📦 Install

Install from npm (package dsh-terminal-panel):

dsh plugin --profile web add dsh-terminal-panel
dsh --profile web

Reload the page once and the terminal icon appears in the sidebar.

Plain JavaScript: no build step, no runtime dependencies. If the package cannot be resolved, the mirror usually has not synced the latest version yet — install once against the official registry, or retry later: dsh plugin --profile web add dsh-terminal-panel --registry=https://registry.npmjs.org/ Requirements: DSH >= 0.2.0-rc.2, Node ^22.19.0 || >=24.0.0, and a host with a working PTY (this plugin uses subprocess.spawnTerminal, i.e. the bundled node-pty).

🚀 Usage

1. Click the terminal icon in the sidebar → the terminal panel opens in the main column.
2. Click + New Terminal → a PTY is allocated immediately in the home directory with the remembered (or default) shell. The ▾ next to it opens the menu: this device at the top, the probed shells grouped by family below, the types that are missing in their own block — choose a shell, type a working directory, or hit ⟳ to re-detect.
3. Type directly in the panel (clicking it focuses the input).
4. Double-click a tab (or use ✎) to rename; ✕ closes the terminal and terminates its process tree.
5. The panel resizes the PTY automatically as the window changes.

Git Bash and cmd

There is nothing to switch on. The host probes %ProgramFiles%\Git\bin\bash.exe, %LOCALAPPDATA%\Programs\Git\bin\bash.exe, scoop roots, and the directory derived from a resolved git.exe (..\bin\bash.exe). Git Bash is offered only when Git for Windows is really installed, and C:\Windows\System32\bash.exe (the WSL launcher) is explicitly excluded — a WSL bash is never passed off as Git Bash. powershell.exe / cmd.exe are verified the same way.

How the shell types are recognised

"Which shells does this machine have" is probed from the host process, never a hard-coded list; it runs again when the panel opens, when you hit ⟳ re-detect, and when the settings are saved:

Types that were not found land in missingShells: the UI shows them under "Not installed" (with a line saying what they are) and the tool output carries a Not installed: … line. The device itself (name · arch · hostname · login shell) is probed by the host and returned alongside, so the same configuration lists different types on different machines.

🧰 Agent tools

On load the plugin registers these tools in the DSH tool registry (globally visible; callable under both the native and ptc presets):

About "wait for the command": a PTY has no shell-integration handshake, so settling is a heuristic and the result says which signal ended the wait — idle (a child process finished and went quiet), quiet (it only went quiet; a long silent command may still be running), exited, timeout. A timeout never kills the command: keep reading with terminal_read(offset=nextOffset), or wait again with a larger idleMs / timeoutMs.

Terminals created by the model and by the user live in one list: you can watch the model's commands in the panel and keep typing in them yourself.

⚙️ Settings

Click the ⚙ in the panel header (present even with no terminals open) to open the settings:

Settings are stored in %DSH_HOME%\terminal-panel\settings.json (by default ~/.dsh/terminal-panel/settings.json); if the file cannot be written the value still applies for this run and the panel says so. Because the settings live on the host, they are shared by every browser and survive a restart.

🧱 Layout

dsh-plugin-terminal-panel/
├── host.js           # Host entry: route carrier, tool attach, reload shell
├── impl.js           # Host implementation: PTY lifecycle, shell probing, SSE, agent tools
├── client.js         # Client: terminal panel, sidebar icon, VT engine, new-terminal menu
├── cordis.patch.yml  # Bundle patch: inserts the plugin row into a profile
└── package.json      # dsh.bundle.patch + dsh.client declarations

How the halves fit together:

sidebar icon / terminal panel (client.js)
        │  same-origin HTTP (loopback)
        ▼
GET  /system-terminals/api/stream?id=…   ← SSE: replay buffer, then live output
POST /system-terminals/api/{list,shells,create,write,read,exec,resize,close,rename,remove}
        ▼
impl.js ── subprocess.spawnTerminal() ──► real PTY (node-pty / ConPTY)
        ▲
        └── ctx.tools.register(terminal_*) ──► agent tools (visible in native and ptc)

The split is deliberate: a loaded ESM module stays cached for the life of the host process, so host.js stays tiny and pulls the logic in through a cache-busted dynamic import(). Replacing impl.js and calling POST /__reload therefore takes effect without restarting DSH. Both the terminal registry and the tool registration live on the impl.js side: a reload takes over the previous registration (the old tools are disposed before the new ones are registered), so a reload neither fails on duplicate names nor orphans running terminals.

Local API

Routes live under /system-terminals/api, bound to DSH's own loopback address and requiring no login (same as other private plugin routes in the ecosystem). Every mutating (POST) route requires an x-dsh-terminal: 1 header: a cross-origin page cannot set a custom header (its preflight is never granted), so no random page you open in the browser can drive your terminals — which matters because POST /exec runs commands.

📝 Changelog

See CHANGELOG.md.

📄 License

MIT © 2026 BaiZhi967