Official2026-05-29
DeepSeek TUI moves the current CodeWhale baseline to v0.8.47 and makes `~/.codewhale` the primary config home
Today's accepted developer signal stays on the TUI track: CodeWhale v0.8.47 is now latest, while the current README and Docker docs switch the primary config and volume path to `.codewhale` with `.deepseek` kept only as a legacy fallback.
Accepted developer update
Today's safe publishable change is on the DeepSeek TUI track again, but it is not just another patch-version bump. The install surface now changed in a way that can break setup and persistence advice if a page still teaches the older home directory.
What changed upstream
- GitHub Releases now marks
v0.8.47as latest on the canonicalHmbown/CodeWhalerepository, dated May 27, 2026. - The rebrand contract is still explicit:
codewhale/codewhale-tuiremain canonical, while legacydeepseek/deepseek-tuibinaries are temporary deprecation shims scheduled to disappear in v0.9.0. - The primary user config home has moved: the current README says user config is now
~/.codewhale/config.toml, with~/.deepseek/config.tomlonly as a legacy fallback. - The project-overlay path moved too: workspace overrides now live at
<workspace>/.codewhale/config.toml, while<workspace>/.deepseek/config.tomlis legacy compatibility only. - Docker persistence moved with the rename: current README examples mount a named
codewhale-homevolume to/home/codewhale/.codewhale, not/home/codewhale/.deepseek. - Skill discovery and bundled system skills now document the new home explicitly: global lookup includes
~/.codewhale/skills, with~/.deepseek/skillsstill listed as legacy compatibility.
Why this matters for crawlable setup pages
- The stable reference point should now be v0.8.47, not v0.8.43.
- Setup pages should teach
~/.codewhaleas the primary config and skill home, while labeling~/.deepseekas a fallback for older installs. - Docker examples should mount
codewhale-home:/home/codewhale/.codewhaleso credentials, sessions, and config persist in the current path. - Pages that explain DeepSeek TUI as a reusable developer environment should mention the new home-directory migration, not only the CodeWhale rename.
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. - Release-title features without anchored docs: the latest release title mentions verification gates, goal tools, and DuckDuckGo, but today's safe editorial delta is the documented install/config-home migration and current release line, not inferred feature behavior.
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.