DTDeepSeek TUI GuideTerminal setup and usage hub
Home/News/DeepSeek TUI Renamed to CodeWhale
Rename Guide

DeepSeek TUI has been renamed to CodeWhale, so the real migration work is command names, package names, and update habits

Most users who land on this question are not confused about branding alone. They want to know whether the install command changed, whether old shell aliases still work, and which docs or automation need to be updated before the compatibility window closes.

Site detail pageDeepSeek TUI Renamed to CodeWhale: Install, Commands, and MigrationNews

Questions this page should answer fast

  • Did the product change or only the name?
  • Which commands and packages should new installs use now?
  • What should you update in scripts, docs, and shell habits before the old shims disappear?

What this page should help you decide

This page should help the reader understand the rename, map old names to current ones, and identify which parts of their setup need an explicit migration.

Fast diagnosis

Branding confusion

Many users still see DeepSeek TUI in search results while upstream docs, releases, and install commands now say CodeWhale.

Command confusion

The rename matters most when the install command, binary name, or package name in your shell no longer matches the official path.

Automation confusion

Shell aliases, docs, CI notes, or local runbooks may still depend on the older names even if the app itself still launches.

Step-by-step workflow

  1. Confirm the current upstream name first
    Treat CodeWhale as the current product name and DeepSeek TUI as the old discovery term.
  2. Switch fresh installs to the new commands
    Use the current install path and current binary name instead of teaching new users the transitional shims.
  3. Audit your local references
    Check shell aliases, scripts, README snippets, CI notes, and internal docs for old command names that should be updated.
  4. Keep compatibility shims temporary
    If you still use old command names in the short term, treat them as transitional and remove them before `v0.9.0` becomes your blocker.

Common mistakes

  • Assuming DeepSeek TUI and CodeWhale are different products instead of a rename transition.
  • Teaching fresh installs with the old command names just because the shims still work today.
  • Forgetting that old command names are documented as temporary and scheduled for removal in `v0.9.0`.

When to leave this page

Leave this page once you know which names are old, which names are current, and whether your next stop should be install, update, troubleshooting, or comparisons.

Use-it-now examples

Start from working examples first, then adjust the details.

Switch the install snippet to the new name

The safest migration move is to update the shared install snippet first so new users do not learn the temporary shim path.

npm install -g codewhale
codewhale --version
codewhale --model auto

Audit one local workflow for old names

Pick one shell alias, one internal doc, and one automation note to verify whether they still mention `codewhale` or `deepseek-tui`.

# search docs and shell aliases
# replace old command names where fresh installs are taught

Common failure branches

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

The old command still works, so your team never updates anything

That creates delayed migration debt. Use the working shim as a bridge, not as a reason to freeze old documentation.

You updated the install command but not the surrounding docs

That leaves the site feeling contradictory. Align install, update, troubleshooting, and comparison pages around the same rename story.