turtle1999/turtle-ui
as is, no warranty
Preserves and packages the original dsh terminal UI so it can be installed as a profile layer instead of building the whole harness. The repository contains the former packages/ui/tui implementation together with its unit and terminal snapshot tests and a dsh profile bundle patch; installing it into a profile activates the TUI as the profile's presentation layer over a normal Harness agent, with the harness still owning models, tools, persistence and the dsh launcher. It is explicitly an artefact of the harness's early history — the README's subtitle is "The first UI of dsh in a Friday afternoon".
Install
⚠️ Upstream documents a local-checkout install — the command it gives is a path on your own machine, so there is nothing pasteable here. See the README for its exact steps.
Compatibility
This is the very first dsh UI, kept as the former packages/ui/tui implementation. The TUI owns terminal presentation and input while DeepSeek Harness owns the agent, model, tools, persistence and the dsh launcher. Its peer APIs come from a sibling Harness checkout, and 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.
Details
- Repo: turtle1999/turtle-ui
- Category: uncategorized
- Stars: 7
- Version: Source checkout only — the repository ships the former packages/ui/tui implementation, its unit and terminal snapshot tests, and the profile bundle patch; no published version
- Last push: 2026-08-13
- First seen: 2026-08-11
Recent updates
There is no release history in the README; the repository is a preserved snapshot of the original TUI plus its bundle patch, and the README documents the sibling-checkout build loop rather than versions.
FAQ
- Do I need the DeepSeek Harness source checkout?
- Yes for building — the README keeps this repository and DeepSeek Harness as siblings (~/git/deepseek-harness and ~/git/turtle-ui) because the peer APIs and the standalone TypeScript/Vitest configurations resolve the sibling sources.
- Why install with file:.?
- The README says to build and install a copied file: package so its Harness peers resolve through the profile's managed fallback, and to re-run the add after rebuilding to refresh the copy.
- Will the GitHub shorthand work?
- The README notes it fails until the allowBuilds key is added; after that it builds and activates.
Alternatives
ccch1mneyyy/dsh-TUI · orriduck/dsh-tui · little-greenbean/dsh-tui