turtle1999/turtle-ui
按现状提供,不提供任何担保。
Project Overview项目介绍
Turtle UI is a native DSH plugin that provides an independent terminal user interface implementation for DeepSeek Harness, extracted from the original packages/ui/tui module of DSH. It handles only terminal presentation and user input processing, while all core agent logic, model calls, tool execution, and data persistence remain managed by the base DeepSeek Harness installation. It ships with its own unit tests and terminal snapshot tests for development validation, follows the DSH native plugin specification, and is packaged as a DSH profile bundle patch that automatically replaces the base DSH interface layer once installed.
This plugin is intended for secondary developers who want to customize or test the terminal interface of DeepSeek Harness. To work on it locally, developers need to clone both this repository and the main DeepSeek Harness repository as sibling directories in the same parent folder. After installing dependencies and building the main DeepSeek Harness project locally, you then install dependencies and build Turtle UI, add it to a dedicated tui profile via the DSH plugin CLI, and launch DSH with the --profile tui flag to load your custom interface.
Turtle UI is released under the permissive open-source BSD-3-Clause license, and uses pnpm as its package manager, requiring pnpm 10 or newer to install and build correctly. When installing directly from GitHub without a local checkout, pnpm v10+ will block the post-install build script by default, so you need to add the printed build allow key to your profile’s pnpm workspace configuration before re-running the install command. Type checking requires access to the sibling DSH source code, so it is only available for local development environments, not end-user installations.
这是一个为 DeepSeek Harness (DSH) 开发的原生终端界面插件,提供原 DSH 内置包 packages/ui/tui 的独立实现,专门负责终端界面展示与用户输入处理,代理逻辑、模型调用、工具调用、持久化存储等核心能力仍由 DSH 本身提供。它符合 DSH 原生插件规范,以配置包补丁的形式安装,激活后会自动替换 DSH 原有界面层。
开发者开发或测试 DSH 终端界面定制功能时,可将本仓库和 DeepSeek Harness 源码放在同级目录,先安装依赖并构建 DeepSeek Harness,再安装依赖构建本插件,之后通过 DSH 的插件命令将本插件添加到独立的 tui 配置档中,启动 DSH 时指定该配置即可加载定制界面。适合需要自定义 DSH 终端交互界面的二次开发者使用。
本插件采用 BSD-3-Clause 许可证开源,使用 pnpm 作为包管理工具,要求 pnpm 版本不低于 10。首次从 GitHub 直接安装时,pnpm 会默认拦截构建脚本,需要用户按照提示将指定密钥添加到配置档的允许构建列表后才能完成安装。类型检查需要依赖同级的 DSH 源码才能运行。
请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】,检查通过再动手。
插件:turtle-ui(turtle1999/turtle-ui)
仓库:https://github.com/turtle1999/turtle-ui
本站详情页:https://www.yhbd.top/plugins/turtle1999-turtle-ui/
本站登记:类型 plugin · 归类 原生 DSH 插件 · 许可证 BSD-3-Clause · ⭐ 10 · 最近提交 2026-08-13 · 主语言 TypeScript
按下面顺序执行,每步先把结论告诉我,再进入下一步:
【1 兼容性检查】
① 我这边:DSH 版本、Node 版本、操作系统、当前 profile(web / desktop)。
② 读它的 README、package.json、插件 manifest,列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对,结论只写「满足 / 不满足 / 未知」三种;不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突:命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。
【2 安全性检查】
① 仓库可信度:和上面「本站登记」是否一致;star / fork 数、创建时间、最近提交,是否归档或长期停更。
② 安装脚本:逐行看 package.json 的 preinstall / install / postinstall,以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名,立刻停下来告诉我,不要继续装。
③ 依赖:列出新增依赖,标出无人维护、或与知名包拼写近似的可疑包(typosquatting)。
④ 权限与副作用:它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限(filesystem / network / shell / clipboard 等),以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限,或权限明显超出功能所需,先停下来问我。
【3 安装】
上面两步没有「不满足」和「高危项」时才执行;用官方推荐方式安装,不要自行提权。
【4 汇报】
用表格输出:检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜,也不要替我决定。
Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH:它会先核对兼容性与安全性(逐条给「满足 / 不满足 / 未知」),确认没问题再安装,有高危项会停下来问你。框内可滚动,复制到的是完整提示词;安装命令不一定准确,发给 DSH 更稳。
- 10 stars - an early-stage project星标 10,属于早期项目
DSH walks through these 9 checksDSH 会逐条核对这 9 项
Compatibility兼容性
- DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
- External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时(Electron / Python / Docker 等)是否齐备
- Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突:命令名、skill / tool 重名、端口占用、重复 MCP 注册
Security安全性
- Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致,是否归档或长期停更
- Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
- curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
- Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
- Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需(filesystem / network / shell / clipboard)
- Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限,以及卸载与回滚方式
Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照,不能替代安全审计。
Or use CLI install (for developers)或使用命令行安装(适合开发者)
CLI Install命令行安装
dsh plugin --profile tui add github:deepseek-harness/turtle-ui
把 turtle1999/turtle-ui 加入你的 DSH 配置(web profile)即可启用。
READMEREADME
Turtle UI
The very first UI of dsh in a Friday afternoon
This repository contains the former packages/ui/tui implementation, its unit and terminal snapshot tests, and a dsh profile bundle patch. The TUI owns terminal presentation and input; DeepSeek Harness owns the agent, model, tools, persistence, and dsh launcher.
Development
Keep this repository and DeepSeek Harness as siblings:
~/git/deepseek-harness
~/git/turtle-ui
Install and build the sibling Harness, then Turtle UI:
(cd ../deepseek-harness && pnpm install && pnpm run build)
pnpm install
pnpm run build
The peer APIs come from the sibling Harness checkout. The standalone TypeScript and Vitest configurations intentionally resolve those sources through ../deepseek-harness; Vitest uses the Harness build for the goal host module instead of mixing that source module with transitive built packages. The patched @earendil-works/pi-tui is a devDependency bundled into lib/ at build time, so consumers install no pi-tui and need no patchedDependencies.
Run
Turtle UI is a dsh profile bundle: its package.json declares "dsh": { "bundle": { "patch": "./cordis.patch.yml" } }, so installing it into a profile activates the patch layer automatically.
From a local checkout, build and install a copied file: package so its Harness peers resolve through the profile's managed fallback. Re-run the add after rebuilding to refresh the copy:
pnpm run build
dsh plugin --profile tui add file:.
dsh --profile tui
From git, with no checkout: the prepare script transpiles lib/ on the consumer's machine during install. pnpm ≥10 blocks that build until you allow it, so the first add fails with an allowBuilds hint; copy the exact key pnpm prints into the profile's pnpm-workspace.yaml and re-run:
dsh plugin --profile tui add github:deepseek-harness/turtle-ui # fails with the allowBuilds key
# add the printed key under allowBuilds in ~/.dsh/profiles/tui/pnpm-workspace.yaml
dsh plugin --profile tui add github:deepseek-harness/turtle-ui # builds and activates
dsh --profile tui
The prepare build (tsdown.prepare.config.ts) transpiles without type checking — the repo's type graph needs the sibling harness checkout, which consumers don't have. pnpm run typecheck in a sibling-checkout environment remains the type gate.
Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要,完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →
ph4310822/dsh-edex-ui
Abyss-Seeker/dsh-plugin-working-status
skymecode/dsh-deep-diving
Small-tailqwq/dsh-deep-whale