DeepSeek TUI keeps its CodeWhale transition active in v0.8.43, with the canonical install path still centered on `codewhale`
Today's accepted developer signal stays on the TUI track: GitHub Releases now marks CodeWhale v0.8.43 as latest, keeps `codewhale` canonical, and leaves the DeepSeek local-deployment and Claude Code tracks unchanged enough to skip publishing new guide claims there.
Accepted developer update
Today's safe publishable change is on the DeepSeek TUI track. The strongest source-backed delta is small but real: the canonical GitHub release line has moved from the May 24 milestone to a newer stable tag, so pages that claim to track the current install surface should not stay pinned to v0.8.42.
What changed upstream
- GitHub Releases now marks
v0.8.43as latest on the canonicalHmbown/CodeWhalerepository. - The rebrand contract is still explicit:
codewhale/codewhale-tuiremain the canonical dispatcher/runtime pair, while legacydeepseek/deepseek-tuibinaries are still temporary deprecation shims scheduled to disappear in v0.9.0. - The canonical Docker path advanced too: the release page now shows
ghcr.io/hmbown/codewhale:v0.8.43, so guide pages should move that pinned example instead of leaving the older 0.8.42 tag in place. - The current README still keeps the practical developer hooks visible: skills discovery order, GitHub-installable skill packs, and self-hosted provider knobs such as
SGLANG_BASE_URLandVLLM_BASE_URLremain part of the documented surface. That matters because DeepSeek TUI is still easiest to rank for when the page explains concrete developer workflows rather than only the rename story.
Why this matters for crawlable setup pages
- The stable reference point should now be v0.8.43, not v0.8.42.
- Canonical install, auth, and doctor examples should lead with
codewhale, not a legacy shim command. - Docker users should see the pinned
ghcr.io/hmbown/codewhale:v0.8.43example. - TUI pages that mention skills or self-hosted runners can safely keep that framing, because the current README still documents both.
What we rejected today
- DeepSeek local development: the official DeepSeek V4 Flash model card still shows the same maintained local baseline already covered on this site: vLLM and SGLang launch commands, Docker Model Runner, OpenAI-compatible curl checks, and the quantization browser for llama.cpp, Ollama, and LM Studio. No stronger official Mac- or guide-shaping delta appeared today.
- DeepSeek in Claude Code / Cloud Code: the official DeepSeek Claude Code guide still uses the same Anthropic-compatible environment recipe already reflected on this site, including
ANTHROPIC_BASE_URL=https://api.deepseek.com/anthropic,deepseek-v4-pro[1m],deepseek-v4-flash,CLAUDE_CODE_SUBAGENT_MODEL, andCLAUDE_CODE_EFFORT_LEVEL=max. - Community-only local runtime and Desktop chatter: useful discovery leads, but not strong enough to publish without a clearer official or reproducible milestone tied to today's three tracked surfaces.
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, stock, or any purchasable inventory surface.