Official2026-05-25

DeepSeek TUI's rename is now official: CodeWhale v0.8.42 is latest, and legacy `deepseek` binaries are only a one-cycle shim

Today's accepted developer signal stays on the TUI track: GitHub Releases now marks CodeWhale v0.8.42 as latest, makes `codewhale` canonical, and limits legacy `deepseek` compatibility binaries to a temporary migration bridge.

Accepted developer update

Today's publishable change is again on the DeepSeek TUI track, but the source-backed milestone is stronger than yesterday's rename-watch framing. The project has now crossed from rename signals into an official release transition.

What changed upstream

  • GitHub Releases now marks v0.8.42 as Latest on the canonical Hmbown/CodeWhale repository, dated May 24, 2026.
  • The release text says the project is renamed to CodeWhale and treats codewhale / codewhale-tui as the canonical dispatcher/runtime pair.
  • Legacy deepseek and deepseek-tui binaries 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.

Why this matters for crawlable setup pages

This is exactly the kind of developer change that belongs on maintained guides:

  1. Canonical install examples should now prefer npm install -g codewhale, cargo install codewhale-cli codewhale-tui --locked, and ghcr.io/hmbown/codewhale:v0.8.42.
  2. deepseek command examples should be labeled as temporary compatibility bridges, not first-choice commands for new installs.
  3. Manual-download instructions should now point at CodeWhale release asset names and the release-specific SHA-256 manifest.
  4. Any page that still implies the rename is only in-progress is now weaker than the official release notes.

What we rejected today

  • DeepSeek local development: the official DeepSeek V4 Flash Hugging Face card and the community teamblobfish/DeepSeek-V4-Flash-GGUF page still show the same maintained local baseline already covered on this site: copyable vLLM/SGLang commands, OpenAI-compatible local serving, llama.cpp fork requirements, quant tables, and hardware notes. Useful, but no stronger new delta today.
  • DeepSeek in Claude Code / Cloud Code: DeepSeek's official Claude Code guide still documents the same Anthropic-compatible environment recipe already reflected in the maintained guide, including ANTHROPIC_AUTH_TOKEN, deepseek-v4-pro[1m], deepseek-v4-flash, CLAUDE_CODE_SUBAGENT_MODEL, and CLAUDE_CODE_EFFORT_LEVEL=max.
  • Stars and popularity growth alone: the repo's 34k+ stars help confirm adoption, but that is not a publishable daily developer update unless tied to a concrete product or install change.

Editorial takeaway

Today's public update belongs on the DeepSeek TUI guide, the dedicated /deepseek-tui landing page, and the news stream. It does not affect stocked plans, pricing cards, or any purchasable inventory surface.

Sources checked

View original source