DTDeepSeek TUI GuideTerminal setup and usage hub
Home/Install/Update Or Upgrade
Update and Upgrade

Updating CodeWhale is simple only after you confirm which package path actually owns the live binary

Most upgrade confusion comes from duplicate installs, rename leftovers, or forgotten PATH history. The right update command is not universal; it depends on the package ecosystem that currently owns the active command your shell resolves first.

Site detail pageUpdate CodeWhale After the DeepSeek TUI RenameInstall

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

  • How do you identify which package path currently owns the binary?
  • When is an upgrade issue actually a duplicate-install issue?
  • What should you verify immediately after upgrading?

What to verify next

  • Confirm `codewhale --version` changed in a fresh shell.
  • Check whether an older install path is still earlier in PATH.
  • If behavior changed unexpectedly, verify config compatibility next rather than reinstalling blindly.

Common mistakes

  • Updating through npm when the binary in use actually comes from cargo or brew.
  • Running multiple upgrade commands and losing track of which one won PATH precedence.
  • Assuming upgrade problems are package-manager issues when the real break is config drift.

Recommended reading order

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

Step 1

Find the active owner

Before running any upgrade command, determine whether npm, cargo, Homebrew, or a manual binary is the actual owner of the current command.

Step 2

Upgrade through one path only

Run the update in that ecosystem first instead of shotgun-updating several package managers.

Step 3

Re-verify the shell after restart

Open a new shell and confirm the version again so you do not mistake cache or PATH order for a successful upgrade.

Use-it-now examples

Start from working examples first, then adjust the details.

Upgrade the same owner you installed with

Do not shotgun-update every package manager. First work out which route actually owns the live binary.

codewhale --version
command -v codewhale || which codewhale
npm install -g codewhale@latest
cargo install codewhale-cli --locked --force
brew upgrade deepseek-tui
codewhale update

Verify after a fresh shell

An upgrade only counts once a new terminal session resolves the same binary at the newer version.

codewhale --version

Common failure branches

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

You upgraded but the version did not change

That usually means you updated the wrong package owner or an older binary still resolves earlier in PATH.

The version changed but behavior got strange

This is often config drift or provider mismatch after upgrade, not a broken package manager. Check config compatibility next.

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.