DTDeepSeek TUI GuideTerminal setup and usage hub
Home/Install/npm
npm Install

Install CodeWhale with npm if you searched for DeepSeek TUI and need the current package name

The project name has changed upstream, but the install question is still mostly about your Node workflow. The npm route is strongest when your machine already manages terminal tools through Node and you want the current CodeWhale package path instead of the older transitional names.

Site detail pageInstall CodeWhale with npm (DeepSeek TUI Rename Guide)Install

DeepSeek TUI has been renamed to CodeWhale

Upstream now ships the project under the new name. For fresh installs, use npm install -g codewhale and launch it with codewhale.

The older deepseek and deepseek-tui names still exist as compatibility shims for now, but upstream documents them as transitional and scheduled for removal in v0.9.0.

Questions this page should answer fast

  • When is npm the right route instead of cargo or Homebrew?
  • What should you verify right after the install finishes?
  • Which failures are actually Node PATH problems rather than CodeWhale problems?

What to verify next

  • Run `codewhale --version` in a fresh shell, not only the one where you installed it.
  • Confirm your API key and provider settings before assuming the install failed.
  • If the command exists but behaves strangely, inspect config and environment variables next.

Common mistakes

  • Installing with one Node version manager and testing in a shell that uses another.
  • Treating provider auth failures as install failures.
  • Updating npm packages but never checking which binary your shell actually calls.

Recommended reading order

Move through the page by workflow need first, then branch into adjacent detail pages or hubs.

Step 1

Confirm the runtime first

Run `node --version` and `npm --version` before you install. If those basics are unstable, the CodeWhale install will not be your real problem.

Step 2

Install globally once

Use a single global npm install path, not a mix of system Node, nvm shells, and copied binaries.

Step 3

Check the active binary

After install, verify that the `codewhale` command resolves to the same global route you think npm owns.

Use-it-now examples

Start from working examples first, then adjust the details.

Fastest npm install path

Use one global npm route, then verify the command from a fresh shell instead of trusting the install window only.

npm install -g codewhale
codewhale --version
command -v codewhale || which codewhale

If you already use nvm or fnm

Install and verify inside the same Node manager shell so package ownership does not split across different runtimes.

node --version
npm --version
npm install -g codewhale
codewhale --version

Common failure branches

Work out which layer failed first instead of treating every problem as the same.

Install command succeeded but `codewhale` is missing

That is usually a PATH or shell-profile problem, not an npm package failure. Go to command-not-found troubleshooting before reinstalling.

`codewhale --version` works in one terminal but not another

Your Node manager or shell startup files are inconsistent across terminal profiles. Compare the active shell first instead of changing the app.

When to leave this page

Once the route is clear, leave this page quickly. Install pages should hand you into config, config pages should send you into provider or troubleshooting, and MCP or mode pages should send you back into live workflow decisions. A detail page is valuable because it narrows the problem, not because you stay on it forever.