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.4 to the package name.

The legacy-peer-deps flag is a temporary npm installation workaround for rc8's dense upstream peer graph. It tells npm to skip peer-conflict enforcement and use this release's explicitly pinned rc8 TUI closure, including the React 18 compatibility peers transitively exposed by upstream's published Web packages. Use this path only with the packed-install-validated release shown here: its gate runs the complete npm ls --all tree and rejects missing, invalid, or conflicting dependencies. Plain npx dsh-claude-tui remains compatible, but a cold npm 10 install can spend close to ten minutes resolving unused Web UI peers. 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 [email protected]
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.

v0.1.4: a real rc8 adaptation

This release pins the complete bundled runtime to DeepSeek Harness 0.1.0-rc.8 and raises the external-runtime floor to >=0.1.0-rc.8 <0.1.1.

• The command bridge now calls rc8's attachment-aware execute(agent, line, images, signal) contract. The current terminal composer deliberately sends an empty image batch; image selection is not being presented as finished TUI functionality.
• Runtime qualification now proves the default-model, Agent, command, and Session services. Its temporary command is executed through the rc8 four-argument envelope, so an rc7-shaped runtime cannot pass by version string alone.
• The bundled graph materializes every required DeepSeek peer used by the TUI plus React 18 peers transitively exposed by upstream's Web graph, and the published shrinkwrap contains one DSH version line only: rc8. No rc6/rc7 fallback is hidden inside the package. A full npm 10 tree may label @img/sharp-wasm32 and @emnapi/runtime as extraneous when their cross-platform optional Sharp parent is filtered; npm ls --all must still exit successfully, and the release gate permits only those optional leaves while rejecting every other dependency problem.
• Users inherit rc8's durable cancelled-response prefix, five-retry default, image safety limits, and other Harness fixes wherever the composed profile uses those services.

[!WARNING]
rc8 changes the SQLite persistence format incompatibly. Do not run different Harness versions concurrently against one $DSH_HOME, and do not downgrade an rc8 Home unless DeepSeek Harness documents a supported migration path. Use a separate Home when testing another version.

See the official rc8 release notes for upstream-wide changes. This project's claims are intentionally narrower: they describe what this TUI composes and verifies.

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.0-rc.8 when no external runtime qualifies.

Compatibility requires both the version range >=0.1.0-rc.8 <0.1.1 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 interaction target is the observed Claude Code 2.1.227 TUI. 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;
• 121/121 tests covering 80x24, 100x30, the rc8 command envelope and live profile probe, packed-tarball installation, both command names, Session resume, approvals, questions, and foreground/background subagents.

The Windows launcher path exists but is not yet release-qualified. 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 terminal-native image attachment intake, 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.