Use the top navigation to choose the topic family first. If you searched for DeepSeek TUI, the most important update is that new installs should use the CodeWhale command names while this site keeps the old keyword as a discoverability bridge.
npm install -g codewhale
codewhale --version
codewhale --model autoThe upstream project has been renamed. For fresh installs, use npm install -g codewhale and launch with codewhale.
Older deepseek and deepseek-tui commands still exist as compatibility shims for now, but upstream documents them as temporary and scheduled for removal in v0.9.0.
These are the main branches in the top menu. Open one branch first, then use the left section menu to move into the exact list page or article.
Use this branch for npm, cargo, Homebrew, Windows, and update routes.
Open install sectionUse this branch for architecture, runtime API, keybindings, runbooks, and mirrored repo topics.
Open docs sectionUse this branch for API keys, providers, file location, environment variables, and reset workflows.
Open config sectionUse this branch for MCP setup, server lists, and example flows after base config already works.
Open MCP sectionUse this branch for plan mode, yolo mode, and the differences between them.
Open modes sectionUse this branch for reusable workflows, examples, and skills vs prompts explanations.
Open skills sectionUse this branch for CodeWhale vs Claude Code and other terminal-agent comparisons.
Open comparisons sectionUse this branch for command-not-found, provider, MCP, and release binary issues.
Open troubleshooting sectionUse this branch for rename explainers, overview pages, and ecosystem context that explain why the tool is still being searched under the old name.
Open news sectionThe site should now behave like a documentation product, not a pile of unrelated landing pages.
Pick Install, Docs, Config, MCP, Modes, Skills, Comparisons, Troubleshooting, or News first.
See a section hubEvery section page and article page now gets a left-side submenu so users can move inside that branch without going back home.
See install listOnce the branch and list are clear, the final click should be a focused detail page like npm install, architecture docs, or API key setup.
See a detail pageThese are the detail pages people most often need after choosing a section.
Best first detail page if you already use Node-based CLI tools.
Open npm articleBest first detail page if the install worked but auth is still unclear.
Open API key articleBest docs detail page if you care about structure rather than just setup.
Open architecture articleBest detail page if you need to choose how cautious or direct the agent should be.
Open modes articleBest first article if your real question is what changed in install commands, package names, and migration guidance.
Open rename articleBest comparison page if you are choosing between terminal-agent workflows.
Open comparison articleBest detail page if the base tool works but the MCP layer still breaks.
Open troubleshooting article