This install hub keeps the old search term, but new installs should use the CodeWhale command names. The practical question is not just which command exists, but which package path best matches your current terminal workflow and update habits.
Upstream has renamed DeepSeek TUI to CodeWhale. For fresh installs, prefer codewhale as the command name and codewhale as the npm package.
The older deepseek and deepseek-tui names still work as compatibility shims for now, but upstream says they are temporary and planned for removal in v0.9.0.
Use this page as the install list first. Pick the package route that matches your machine and workflow, then open the detail guide.
Choose npm first if you already use Node-based CLI tools and want the shortest route to a working command.
Go to npm installChoose Homebrew or release binaries if you care more about system package habits than the quickest first run.
Go to Homebrew installChoose cargo if you already live in the Rust toolchain and want CodeWhale to fit that environment.
Go to cargo installOpen the exact install detail page you need instead of hopping between unrelated package manager examples.
The npm route is the most approachable for many CLI users who already manage agent tools globally through Node.
Open npm guideThe cargo route matters if you want the Rust ecosystem path and need the current codewhale-cli --locked install command explained clearly.
Homebrew is useful if you want a cleaner system-level install path and already manage CLI tools through brew.
Open Homebrew guideUse this page when shell defaults, PowerShell, Git Bash, or WSL make the install route feel less obvious than macOS examples suggest.
Open Windows install guideUse this page when the real issue is not first install, but how to keep the active command current without mixing package paths.
Open update guide