Official2026-05-25
DeepSeek TUI Rename Lands in CodeWhale v0.8.42
GitHub Releases now marks CodeWhale v0.8.42 as latest, makes `codewhale` canonical, and limits legacy `deepseek` compatibility binaries to a temporary migration bridge.
What changed upstream
- GitHub Releases now marks
v0.8.42as Latest on the canonicalHmbown/CodeWhalerepository, dated May 24, 2026. - The release text says the project is renamed to CodeWhale and treats
codewhale/codewhale-tuias the canonical dispatcher/runtime pair. - Legacy
deepseekanddeepseek-tuibinaries are no longer just informal compatibility aliases. The release explicitly says they are deprecation shims for one release cycle, printing a warning and forwarding to the canonical binaries. - The removal boundary is now documented: upstream says those legacy shims will be removed in v0.9.0.
- The public website still lags behind GitHub: deepseek-tui.com remains branded as DeepSeek TUI and still teaches older
deepseek-named install paths, which means setup pages now need to explain the split as an official transition rather than a vague naming drift.
Practical setup guidance
This is exactly the kind of developer change that belongs on maintained guides:
- Canonical install examples should now prefer
npm install -g codewhale,cargo install codewhale-cli codewhale-tui --locked, andghcr.io/hmbown/codewhale:v0.8.42. deepseekcommand examples should be labeled as temporary compatibility bridges, not first-choice commands for new installs.- Manual-download instructions should now point at CodeWhale release asset names and the release-specific SHA-256 manifest.
- Any page that still implies the rename is only in-progress is now weaker than the official release notes.