This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.

Quick start

dsh-tianshu-tui

— source: plugin_wiki.wiki_content

Install & verify

dsh plugin --profile web add @huiliyi37/dsh-tianshu-tui

Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.

— source: plugins.install

Key points

• Node.js ^22.19 || >=24
• PATH 上有 pnpm（dsh plugin 会转发给它）
• 输入框长文本性能 — 折行逐字符量宽走缓存（10 万字符草稿每次按键 ~1.3s → ~10ms）；粘贴可编辑阈值抬至 100 行/10000 字（此前 10 行即收成标记）；输入视窗 16 行上限（超出折叠「… 上/下 N 行」）；Home/End/Ctrl+U/K 以逻辑行为范围、PageUp/Down 翻页、↑↓ 按软折行移动；换行模式下粘贴并入草稿不提交
• Ctrl+C 连按退出无死角 — 窗口内第二次恒退出（有草稿时第一次清空、Ctrl+Z 可恢复）；打断中第二次直接退出不用等落定；vim normal 下 Esc 空操作不再误弹 rewind；Kitty 键盘协议 CSI u 完整解码（Ctrl+C=CSI 99;5u、release 事件去重）
• 活区卡片语言统一 — 工具卡/委派树/后台任务一套符号：进行中 ⠋、成功 ›、失败 ✗、正文 ⎿；终态行后退（muted）；正在跑的子代理和 build 终于长得像同类对象

— source: plugin_wiki.readme_en (fallback readme_raw)

FAQ

Will this plugin conflict with the official web client? Can they be installed at the same time?

No conflict. This plugin is a Cordis bundle patch, mounted on dsh-base, using the same Agent, model, session and tool services; it can be installed in the same profile as dsh-web-app, with session/event sharing the same true source (README.md:78-83 / cordis.patch.yml:1-7).

Will uninstalling the plugin lose existing sessions? Will it modify the harness core?

No. This plugin does not modify DeepSeek Harness core code; TUI's own preferences and input history are stored in ~/.dsh-tui/, which can be manually deleted after uninstallation (README.md:316-325 / docs/getting-started.md:32-50).

What to do when startup shows ERR_FS_EISDIR / Path is a directory .../@deepseek-ai/dsh?

This is an old installation fallback in ~/.dsh/profiles/node_modules conflicting with the official CLI. Simply reinstall with a clean DSH_HOME directory: DSH_HOME=/tmp/dsh-tianshu npx -y @deepseek-ai/[email protected] plugin --profile tui add @huiliyi37/dsh-tianshu-tui (README.md:67-72 / docs/getting-started.md:54-60).

I pasted an image but the model says it can't see it?

When the primary model cannot recognize images, you need to install the vision bridge plugin dsh-vision-bridge (provides visionBridge service) or explicitly inject vision configuration in the installation recipe; if neither is present, the image won't be sent and a warning will be displayed, which is intentional fails loud behavior (README.md:259 / docs/getting-started.md:68-70).

Why do LSP diagnostics only show on the TUI screen, but the model can't see them?

The LSP bridge in this plugin is a presentation-layer local bridge: diagnostics only go to tool card badges and the /lsp panel, not registered to the model's tool surface; if you need the model to use tools like lsp_goto_definition, install omdsh-dev/dsh-lsp (README.md:96 / docs/getting-started.md:72-74).

How to disable the npm update check at startup?

Set the environment variable DSH_TUI_SKIP_UPDATE=1 to skip it; copies installed via github: or link: won't be rewritten into npm packages (README.md:53 / docs/configuration.md:30-38).

Do I have to exit and manually restart after an update?

Since 0.1.2-rc.10, when a session hasn't started work yet, the auto-update will automatically restart after writing to disk; when the session is not empty or autoRestartOnUpdate is disabled, it only prompts, and you can manually input /restart (README.md:106 / src/index.ts:177-189).

Can it run on Windows? What should I note?

Yes. Ctrl+C interruption generates both 0x03 byte and SIGINT signal; version 0.1.2-rc.10 added dual SIGINT registration and deduplication to prevent "input box disappearing" (README.md:110 / src/index.ts:144-160).

— source: plugin_wiki.faq_json

Compatibility

• DSH: 0.1.0-rc.7+
• Node: ^22.19 || >=24
• Platforms: macOS, Windows, Linux

— source: plugin_wiki.compatibility_json

Pitfalls

Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.

— source: general rule