Files
codewhale/docs/INSTALL.md
T
Claude 0e5afe0b01 feat(v0.8.8): linux ARM64 prebuilts + install docs overhaul
Triggered by a Telegram report from a Chinese user trying to deploy
DeepSeek TUI on a HarmonyOS ARM64 thin-and-light: `npm i -g deepseek-tui`
exited with `Unsupported architecture: arm64 on platform linux` because
v0.8.7 only published x64 Linux artifacts. They worked around it with
`cargo install`, but the README never documented that path for ARM users.

This PR closes that gap on three layers:

- **Release workflow** — add `aarch64-unknown-linux-gnu` to the build
  matrix using GitHub's `ubuntu-24.04-arm` runner. v0.8.8 will publish
  `deepseek-linux-arm64` and `deepseek-tui-linux-arm64` alongside the
  existing x64/macOS/Windows assets, plus add the row to the Release
  body's manual-download table.

- **npm wrapper** — uncomment the linux/arm64 row in `ASSET_MATRIX`,
  rewrite the `Unsupported architecture/platform` error to print the
  full `cargo install deepseek-tui-cli deepseek-tui --locked` recipe
  and link to docs/INSTALL.md, and add `DEEPSEEK_TUI_OPTIONAL_INSTALL=1`
  so CI matrices that include unsupported platforms can keep running
  without a binary.

- **Docs** — new docs/INSTALL.md covering every supported platform,
  prebuilt vs. cargo install vs. manual download, cross-compiling x64
  -> ARM64 with `cross` or `gcc-aarch64-linux-gnu`, China mirror setup,
  and a troubleshooting section for the common arm64, MISSING_COMPANION_BINARY,
  and self-update arch-mapping (#503) errors. README and README.zh-CN
  now have an explicit Linux ARM64 quickstart pointing at `cargo install`
  for v0.8.7 today and `npm i -g` for v0.8.8+; the v0.8.7 known-issue
  block is updated to mention both #503 and the missing arm64 prebuilt.

https://claude.ai/code/session_01Fg1FKMtDxVnC4pp6bNBRCS
2026-05-03 04:42:53 +00:00

9.4 KiB

Installing DeepSeek TUI

This page covers every supported install path and the most common "it didn't install" failures, including Linux ARM64 and other less common platforms.

If you just want the short version, see the main README or 简体中文 README.


1. Supported platforms

deepseek-tui ships prebuilt binaries for these platform/architecture combinations from v0.8.8 onward:

Platform Architecture npm install cargo install GitHub release asset
Linux x64 (x86_64) deepseek-linux-x64, deepseek-tui-linux-x64
Linux arm64 deepseek-linux-arm64, deepseek-tui-linux-arm64
macOS x64 deepseek-macos-x64, deepseek-tui-macos-x64
macOS arm64 (M-series) deepseek-macos-arm64, deepseek-tui-macos-arm64
Windows x64 deepseek-windows-x64.exe, deepseek-tui-windows-x64.exe
Other Linux (musl, riscv64, …) ¹ ² build from source
FreeBSD / OpenBSD ² build from source

¹ The npm package will exit with a clear error and point you here. ² Provided your toolchain can compile a recent Rust workspace; see Build from source below.

Linux ARM64 note (v0.8.7 and earlier). v0.8.7 and earlier do not publish a Linux ARM64 prebuilt; users on HarmonyOS thin-and-light, Asahi Linux, Raspberry Pi, AWS Graviton, etc. saw Unsupported architecture: arm64 from npm i -g deepseek-tui. v0.8.8 publishes both deepseek-linux-arm64 and deepseek-tui-linux-arm64, so a plain npm i -g deepseek-tui works on any glibc-based ARM64 Linux. If you're stuck on v0.8.7, jump to Build from sourcecargo install works fine.


npm install -g deepseek-tui
deepseek

postinstall downloads the right pair of binaries from the matching GitHub release, verifies a SHA-256 manifest, and exposes both deepseek and deepseek-tui on your PATH.

Useful environment variables:

Variable Purpose
DEEPSEEK_TUI_VERSION Pin which release the wrapper downloads (defaults to deepseekBinaryVersion)
DEEPSEEK_TUI_GITHUB_REPO Point the downloader at a fork (owner/repo)
DEEPSEEK_TUI_RELEASE_BASE_URL Override the download root (e.g. an internal mirror or release-asset proxy)
DEEPSEEK_TUI_FORCE_DOWNLOAD=1 Re-download even if a cached binary marker matches
DEEPSEEK_TUI_DISABLE_INSTALL=1 Skip the postinstall download entirely (CI smoke, vendored binaries)
DEEPSEEK_TUI_OPTIONAL_INSTALL=1 Don't fail npm install on download/extract errors — useful in CI matrices

3. Install via Cargo (any Tier-1 Rust target)

If GitHub releases are slow, blocked, or you're on an unsupported architecture, install from crates.io directly. Both crates are required — the dispatcher delegates to the TUI runtime at runtime.

# Requires Rust 1.85+ (https://rustup.rs)
cargo install deepseek-tui-cli --locked   # provides `deepseek`
cargo install deepseek-tui     --locked   # provides `deepseek-tui`
deepseek --version

China / mirror-friendly Cargo registry

# ~/.cargo/config.toml
[source.crates-io]
replace-with = "tuna"

[source.tuna]
registry = "sparse+https://mirrors.tuna.tsinghua.edu.cn/crates.io-index/"

rsproxy, Tencent COS, and Aliyun OSS mirrors work the same way; pick whichever is fastest from your network.


4. Manual download from GitHub Releases

Grab the matching pair of binaries for your platform from the Releases page and drop them side by side into a directory on your PATH (e.g. ~/.local/bin):

# Linux ARM64 example
mkdir -p ~/.local/bin
curl -L -o ~/.local/bin/deepseek      \
    https://github.com/Hmbown/DeepSeek-TUI/releases/latest/download/deepseek-linux-arm64
curl -L -o ~/.local/bin/deepseek-tui  \
    https://github.com/Hmbown/DeepSeek-TUI/releases/latest/download/deepseek-tui-linux-arm64
chmod +x ~/.local/bin/deepseek ~/.local/bin/deepseek-tui
deepseek --version

Verify integrity against the per-release SHA-256 manifest:

curl -L -o /tmp/deepseek-artifacts-sha256.txt \
    https://github.com/Hmbown/DeepSeek-TUI/releases/latest/download/deepseek-artifacts-sha256.txt
( cd ~/.local/bin && sha256sum -c /tmp/deepseek-artifacts-sha256.txt --ignore-missing )

(Use shasum -a 256 -c instead of sha256sum on macOS.)


5. Build from source

This is the catch-all for any platform we don't ship — including musl, riscv64, LoongArch, FreeBSD, and pre-2024 ARM64 distros.

Prerequisites

  • Rust 1.85 or later — install with rustup.
  • Linux build-time deps (Debian/Ubuntu/openEuler/Kylin):
    sudo apt-get install -y build-essential pkg-config libdbus-1-dev
    # openEuler / RHEL family:
    # sudo dnf install -y gcc make pkgconf-pkg-config dbus-devel
    
  • A working cmake is not required.

Build and install

git clone https://github.com/Hmbown/DeepSeek-TUI.git
cd DeepSeek-TUI

cargo install --path crates/cli --locked   # provides `deepseek`
cargo install --path crates/tui --locked   # provides `deepseek-tui`

deepseek --version

Both binaries land in ~/.cargo/bin/ by default; make sure that directory is on your PATH.

Cross-compiling from x64 to ARM64 Linux

If you want to build an ARM64 Linux binary on an x64 Linux host (e.g. for a HarmonyOS / openEuler ARM64 thin-and-light), use cross, which wraps the official Rust cross-targets in a Docker container:

# Once
rustup target add aarch64-unknown-linux-gnu
cargo install cross --locked

# Per build
cross build --release --target aarch64-unknown-linux-gnu -p deepseek-tui-cli
cross build --release --target aarch64-unknown-linux-gnu -p deepseek-tui

The resulting binaries land in target/aarch64-unknown-linux-gnu/release/deepseek and target/aarch64-unknown-linux-gnu/release/deepseek-tui. Copy the matched pair to the ARM64 host (e.g. via scp) and chmod +x them.

If you don't have Docker available, install the cross-linker directly and let Cargo do the work:

sudo apt-get install -y gcc-aarch64-linux-gnu
rustup target add aarch64-unknown-linux-gnu

cat >> ~/.cargo/config.toml <<'EOF'
[target.aarch64-unknown-linux-gnu]
linker = "aarch64-linux-gnu-gcc"
EOF

cargo build --release --target aarch64-unknown-linux-gnu -p deepseek-tui-cli
cargo build --release --target aarch64-unknown-linux-gnu -p deepseek-tui

The same recipe works for aarch64-unknown-linux-musl if your distro is musl-based.


6. Troubleshooting

Unsupported architecture: arm64 on platform linux

You're on a release earlier than v0.8.8 that doesn't publish Linux ARM64 binaries. Either upgrade (npm i -g deepseek-tui@latest) or use cargo install per Section 3.

MISSING_COMPANION_BINARY at runtime

The dispatcher (deepseek) requires the TUI runtime (deepseek-tui) to be on the same PATH. If you installed only one crate via cargo install, install both:

cargo install deepseek-tui-cli --locked
cargo install deepseek-tui     --locked

deepseek update reports no asset found for platform deepseek-linux-aarch64

This is #503 in v0.8.7 — the self-updater used Rust's aarch64/x86_64 arch names instead of the release artifact's arm64/x64. Workaround until v0.8.8:

npm i -g deepseek-tui@latest
# or
cargo install deepseek-tui-cli --locked

npm download is slow or times out from mainland China

Set DEEPSEEK_TUI_RELEASE_BASE_URL to a mirrored release-asset directory (rsproxy, TUNA, Tencent COS, Aliyun OSS), or skip npm entirely and use the Cargo mirror setup in Section 3.

Debian/Ubuntu: error: linker 'cc' not found while building

Install the C toolchain:

sudo apt-get install -y build-essential pkg-config libdbus-1-dev

Wrapper installs but deepseek isn't found

npm i -g installs into $(npm prefix -g)/bin; make sure that directory is on your shell's PATH. With nvm: nvm use --lts && hash -r.


7. Verifying your install

deepseek --version
deepseek doctor       # checks API key, provider, runtime, and PATH integrity
deepseek doctor --json

doctor exits non-zero if it finds a problem and prints structured remediation hints. Paste the JSON output into a GitHub issue if you need help.