DSH Claude TUI

A Claude Code-style terminal workflow, powered by DeepSeek Harness.

English · 简体中文

Start in one command. Use real DSH models, Sessions, tools, approvals, and subagents
through a familiar, high-fidelity terminal interface.

[!NOTE] This is an independent community project. It is not affiliated with, endorsed by, or sponsored by Anthropic or DeepSeek. “Claude Code” identifies the version-pinned interaction target; no Anthropic source code is included. See the trademark and compatibility notice.

Start in one command

Requires Node.js 22.19+ or 24+.

npx --yes --legacy-peer-deps dsh-claude-tui

That command installs and opens the TUI selected by npm's latest tag. You do not need a global dsh, a repository checkout, pnpm, or manual profile setup. To pin this release exactly, add @0.1.6 to the package name.

The legacy-peer-deps flag avoids npm's expensive resolution of unused upstream Web UI peers. It skips peer-conflict enforcement; this release explicitly includes the required TUI services and pins its DSH dependencies. The installed-package gate checks the complete npm ls --all tree and rejects missing, invalid, or conflicting dependencies. Plain npx dsh-claude-tui is also qualified with ordinary npm peer resolution, though a cold installation can take several minutes. The flag does not change the DSH runtime version or TUI behavior.

A real model request needs credentials for the DSH provider you select. Use /provider to inspect or enter credentials and /model (or Option+P / Alt+P) to switch among the models and effort levels exposed by DSH.

For repeat use:

npm install --global --legacy-peer-deps dsh-claude-tui@0.1.6
dshtui

The global install exposes both dshtui and the canonical dsh-claude-tui command. Resume work with dshtui --resume for the Session picker, or --resume <session-id> for an exact Session.

DSH 0.1.2-rc.1 support

Version 0.1.6 pins the bundled Harness to 0.1.2-rc.1 and accepts external runtimes in >=0.1.2-rc.1 <0.1.3 only after a behavioral probe. Version 0.1.5 uses the previous 0.1.1-rc.2 runtime. See the v0.1.6 release notes for upgrade guidance.

• Session replay uses snapshotEvents(). The runtime probe appends a real event and checks seq, eventAt(), snapshot readback, and persistence flush.
• Structured questions use DSH's Agent-scoped user-questions/request waterfall. Model/provider configuration uses the current settings API.
• PTC mode now uses upstream's ptc value. The launcher and bundle still accept DSH_TOOLS_MODE=code as an alias. Native and Both modes remain selectable.
• Cordis, loader, group, and schema peers match the new Harness graph. The production shrinkwrap contains only the 0.1.2-rc.1 DSH line.
• The existing image composer, durable attachments, plan toggle, transcript timing, approvals, and Session picker are retained.

To run from a checkout:

corepack pnpm install --frozen-lockfile
corepack pnpm build
DSH_HOME=/tmp/dsh-claude-tui-rc1 DSH_CLAUDE_TUI_RUNTIME=bundled node lib/cli.js

DSH has an extensive official documentation site. This repository maintains a bilingual official documentation mirror pinned to the supported release, with a full index, source hashes, license notices, and docs:dsh:sync / docs:dsh:check commands. CI checks the snapshot offline. The mirror is repository-only and is excluded from the npm tarball.

[!WARNING] Upstream 0.1.2 removes the optional SQLite Session persistence backend; export sessions stored by that backend using the old Harness before upgrading. SQLite query/index storage is separate. Use separate Homes when testing different Harness versions; this adapter does not add a downgrade or SQLite export migration.

See the official release notes and adaptation validation for the exact scope and evidence. Upstream Web features do not imply corresponding TUI features.

What you get

The TUI reads capabilities from DSH rather than hardcoding model, effort, credential, or approval behavior. Harness remains the source of truth; Claude-only cloud services, account state, model behavior, and private permission semantics are not simulated.

Everyday controls

Run /help inside the TUI for the current command list.

Works with an existing DSH setup

The default launcher removes the need to choose an installation strategy up front:

1. Reuse a compatible DSH already associated with the selected $DSH_HOME, or a verifiable dsh on PATH.
2. Probe it in an isolated, credential-free temporary Home.
3. Fall back to the bundled, shrinkwrap-pinned DSH 0.1.2-rc.1 when no external runtime qualifies.

Compatibility requires both the version range >=0.1.2-rc.1 <0.1.3 and a successful behavioral probe. When a Home can be shared safely, existing credentials, Sessions, settings, and unrelated profiles remain available. The launcher does not overwrite an unowned profile. An unsafe implicit default can fall back to ~/.dsh-claude-tui with a visible notice; an explicit DSH_HOME conflict fails with an actionable error instead of silently moving data.

See Launcher environment compatibility for the complete selection, ownership, and recovery contract.

Compatibility and verification

The main interaction target is the observed Claude Code 2.1.227 TUI; the [Image #1] Ctrl+V composer behavior was independently observed against Claude Code 2.1.237. Current qualification covers:

• macOS arm64 and Linux x64;
• true-color, xterm-compatible terminals;
• 24 independently captured PTY reference frames and 22 automated visual/semantic anchors;
• Automated tests covering 80x24, 100x30, clipboard/attachment failure and cancellation paths, the attachment-aware command envelope and live profile probe, packed-tarball installation, macOS Shift+Tab through a real PTY, both command names, Session resume, approvals, questions, and foreground/background subagents. An additional opt-in macOS system-clipboard gate sends an installed-package image through DSH storage and a local Files API/chat mock.

The Windows launcher, junction, signal-forwarding, VT-input, dependency-prebuild, and STA image-clipboard paths are implemented, and the pinned DSH upstream has a native Windows gate. This TUI's own CI still runs only on Ubuntu, however, and no Windows packed-TUI/ConPTY UAT has been recorded. Windows is therefore an implemented but currently unqualified target, not a supported release platform. Read the full visual and semantic qualification report or the artifact-hardening baseline.

Build it with us

This project should be more than a theme layered over a runtime. The goal is a fast, inspectable terminal client that respects DSH semantics and gives developers a great place to improve the Harness experience together.

You do not need to know the entire runtime to contribute. Useful entry points include:

Start with the contribution guide, then open a focused issue or pull request. For a larger change, propose the user problem and evidence first so maintainers and contributors can shape the seam together.

Develop locally

corepack pnpm install --frozen-lockfile
corepack pnpm check

The release gate runs TypeScript validation, a clean production build, then the complete serial Vitest suite. Visual-parity changes must include an independently captured reference or a documented Harness-semantic boundary. Runtime changes must prove the installed package path, not only source imports.

Near-term opportunities include richer image composition, file and Session reference completion, broader Session management, more plan/todo/background-job states, and qualification across more terminals and operating systems. These are contribution directions, not claims about shipped behavior.

License

Original project code is available under the MIT License. Product names and marks remain the property of their respective owners; the MIT License does not grant rights to third-party trademarks.