Interactive terminal tab in the Conversation view row: one persistent shell per session opened straight in its working directory, reload reconnects with the screen intact, and an explicit close stays closed across refreshes. Shares its shells and default-shell setting with the sidebar terminal.
Install
# from npm (prebuilt)
dsh plugin --profile web add dsh-terminal-tab
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:jayhchen/dsh-terminal-tab
Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).
README
dsh-terminal-tab
A terminal tab for the Conversation view row of DeepSeek Harness (DSH) — the same persistent shells as the sidebar terminal, mounted as a top tab.
Adds a Terminal tab to the top row where "Conversation / Trace" live (after Conversation, before Trace). It behaves exactly like the sidebar terminal — same persistent shells, same auto-recovery — just with the entry point moved to the top.
Works with DSH 0.2.2-rc.2 and later 0.2.x releases.
Features
- Opens straight into a shell: one fixed terminal per session, started in the session's current working directory
- Auto-recovery: refresh the page or reopen the browser and the terminal reconnects, screen content intact
- Never reclaimed: switching tabs or sessions never kills it — the terminal keeps running as long as the window stays open
- Explicit close: the floating close button (top-right) ends the process; the "closed" state survives page refreshes until you click "New terminal"
- Default shell: switch it in Settings → Plugins → Installed →
dsh-terminal-tabdetail page; sidebar terminals follow the same choice - After a service restart: shows "This terminal no longer exists" with a one-click recreate
- The top tab and the sidebar share the same pool of terminal processes
Installation
Web:
dsh plugin --profile web add dsh-terminal-tab
dsh plugin --profile web update dsh-terminal-tab
Desktop:
dsh plugin --profile desktop add dsh-terminal-tab
dsh plugin --profile desktop update dsh-terminal-tab
License
Links
More in this category
zhu1090093659/dsh-web#packages/dsh-task-board★ 10458
Task board for the dsh web GUI: a sidebar multi-column kanban whose cards run in real DSH agent sessions and can also be scheduled with cron expressions, executed host-side even with the browser closed.
zhu1090093659/dsh-web#packages/dsh-web-all★ 10458
Plugin and skin collection for the DSH Web UI: task board, Git graph, right-side panel, remote mobile UI, pet, live token stats, and a skin center.
ccch1mneyyy/dsh-TUI★ 7797
Claude Code-style full-screen terminal UI: pixel-whale header, live status line, and streaming thought expansion.
MeteorNOX/DeepSeek-Balance-Whale-Widget★ 7271
A fixed-corner whale widget for the DSH web GUI — balance, today's usage and per-turn cost with peak/off-peak pricing, editable balance-alert and daily-budget bubbles, a module-based custom bubble queue with A/B weighted choices and random lines or images, 30+ vendor templates (OpenAI, OpenRouter, Kimi, SiliconFlow, Ark, Zhipu, MiniMax and more) with per-model balance and subscription quota, plus task-end sound, imported audio, custom roles and a resource manager. Local-only, no telemetry.
omdsh-dev/DSH-better-sidebar★ 5191
Full sidebar workbench with file rendering and editing, terminal, Git, and subagents; third-party plugins can register new tabs.
omdsh-dev/dsh-genui★ 1007
Interactive UI components rendered inline in replies: layout, charts, forms, quizzes, mermaid, 3D scenes, and an action event loop back to the model.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.