turtle1999/turtle-ui 预览 preview

turtle1999/turtle-ui

Plugin插件 Native原生 ⭐ 10 BSD-3-Clause UI & Themes界面与主题Dev Workflow开发与代码工作流

按现状提供,不提供任何担保。

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 源码才能运行。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 1 note1 项提示
  • 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 →

← 上一个 Prev dsh-archive-manager 下一个 Next dsh-tidychat →