Install DeepSeek TUI

What you are installing

DeepSeek TUI ships as real binaries (typically accessed via deepseek and deepseek-tui). Some installers bundle both; others require two commands. If only half installs, you may see errors about a missing companion binary—fix by reinstalling with the method below that matches your platform.

Method 1: npm (common default)

npm install -g deepseek-tui

Works well if you already have Node for other reasons. The package typically downloads native binaries—runtime behavior is not Node.js-based day to day.

If npm downloads are slow in your region, try your preferred registry mirror, then rerun the command.

Method 2: Cargo

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

Use Cargo when you manage Rust tooling already. The --locked flag reduces dependency drift between installs.

Method 3: Homebrew (macOS)

brew tap Hmbown/deepseek-tui
brew install deepseek-tui

Good fit when you want easy upgrades through brew on Apple Silicon or Intel Macs.

Method 4: Windows (Scoop)

scoop install deepseek-tui

Use Windows Terminal for best rendering. WSL2 is another solid choice if you prefer Linux tooling.

Method 5: Docker

docker run --rm -it \
  -e DEEPSEEK_API_KEY \
  -v "$PWD:/workspace" \
  ghcr.io/hmbown/deepseek-tui:latest

Useful for sandboxes or repeatable demos—not always the gentlest first-time path.

Authenticate

Most users store a DeepSeek API key. You can set it through the CLI or environment variables—pick one style and stay consistent across shells.

deepseek auth set --api-key sk-your-key-here

Or export for the session:

export DEEPSEEK_API_KEY=sk-your-key-here

Other providers (OpenRouter, Fireworks, Ollama, etc.) use different variable names—see Configuration for the full table.

Verify the install

deepseek --version
deepseek-tui --version
deepseek doctor

If versions print and doctor passes, move on to Quick start.

Common problems

Missing companion binary

Re-run install steps so both parts land on your PATH.

API key not picked up

Confirm the variable exists in the same terminal session—or configure auth via CLI instead of env vars.

Blank or glitchy UI

Switch to Windows Terminal, iTerm2, or another modern emulator; integrated terminals sometimes mishandle mouse capture.

You wanted GGUF / local weights instead

Jump to Local deployment—installation alone won’t magically bundle giant checkpoints.

Next steps

• Quick start — first session walkthrough.
• Configuration — config.toml, modes, hooks.
• Modes — Plan vs Agent vs YOLO in depth.