DeepSeek TUI Enters the CodeWhale Rename Transition

What changed upstream

• The public website still presents the legacy path: the DeepSeek TUI homepage and install page still show the DeepSeek TUI brand, the deepseek command, the deepseek-tui npm package, and v0.8.40 as the latest stable release.
• The live project activity feed now shows a CodeWhale rename sequence: the same official website currently highlights recent upstream work titled roughly as README/docs rename to CodeWhale, npm publish as codewhale while keeping deepseek-tui as a deprecation shim, and binary renames that keep deepseek aliases.
• GitHub has already moved further than the public site: the canonical GitHub repo path for the project now redirects from Hmbown/DeepSeek-TUI to Hmbown/CodeWhale.
• Compatibility remains the explicit bridge: the rename wave is not described as an overnight hard cut. The project-owned surfaces indicate compatibility aliases are being kept so existing deepseek users do not break immediately.

Practical setup guidance

This is a better developer signal than a vanity version bump because it changes what a technically trustworthy setup page should tell readers today:

1. Do not pretend there is only one canonical command spelling across all official-looking pages right now.
2. If you follow the public website today, the documented install path is still deepseek / deepseek-tui.
3. If you follow the redirected GitHub repo and newer rename work, you will start seeing codewhale naming.
4. Safer setup advice should tell readers to stay on one verified command surface at a time and not mix package names, binary names, and repo paths from different rename stages.

Sources

• DeepSeek TUI homepage
• DeepSeek TUI install page
• CodeWhale GitHub repository
• DeepSeek official Claude Code integration guide
• DeepSeek V4 Flash model card