DeepSeek TUI and CodeWhale are the same project
CodeWhale is the current upstream name. DeepSeek TUI remains the established public and search-facing name used by older releases, commands, and tutorials.
DeepSeek TUI Project Identity
DeepSeek TUI and CodeWhale are the same terminal coding-agent project
This page explains the rename, current and legacy name compatibility, API-client boundary, capabilities, and limitations. Installation, configuration, and troubleshooting live in the paired guide.
Current and legacy names can coexist
Fresh installs should follow current CodeWhale package and config names. Existing machines may still expose deepseek commands or .deepseek state, so identify the installed version before migrating.
It is an API agent, not a local model runner
The terminal agent reads and edits projects but sends model requests to the DeepSeek API. Local V4 Flash execution belongs to the separate local-deployment workflow.
DeepSeek TUI installation guide
Install DeepSeek TUI with the current CodeWhale command
Install the current CodeWhale command for the DeepSeek TUI project, configure a DeepSeek API key, verify the active binary and config directory, choose a safe work mode, and troubleshoot common setup failures.
Use the guide for current installation commands, API-key setup, configuration paths, operating modes, verification, and troubleshooting. It links back here for naming and compatibility.
Open the installation guideVerified summary
What is accurate about DeepSeek TUI today
| Question | Answer | Why it matters |
|---|---|---|
| Are DeepSeek TUI and CodeWhale different products? | No. CodeWhale is the current upstream name for the project that users originally discovered as DeepSeek TUI. | One canonical explanation prevents two names from competing as separate products. |
| Which name should a fresh install use? | Use the current CodeWhale package, binary, and config-home names shown in the installation guide. | Mixing current release assets with legacy commands creates avoidable path and credential errors. |
| Why do deepseek commands still appear in tutorials? | Older releases and compatibility shims used deepseek or deepseek-tui names, and older machines may still retain them. | Legacy names are migration context, not proof of a second project. |
| Is this an official DeepSeek Inc. product? | No. It is an independent open-source terminal agent that connects to the public DeepSeek API. | The distinction avoids implying vendor ownership or support that does not exist. |
| Does the project run DeepSeek models locally? | No. It runs agent tools locally but sends model requests to the configured DeepSeek API endpoint. | Terminal execution and local model inference are different workflows. |
DeepSeek V4 Flash locally
Use the local-deployment page when you want model inference on your own hardware rather than an API coding agent.
Check local feasibilityDeepSeek vs Claude
Compare the model ecosystems after deciding which terminal workflow and compatibility boundary fits your project.
Compare the modelsIn-stock Coding Plans
Check current inventory if you need API access. Products appear as purchasable only while compatible stock exists.
Check current inventoryFAQ
DeepSeek TUI naming questions
Should I install DeepSeek TUI or CodeWhale?
They are the same project. For a fresh setup, follow the current CodeWhale commands in the linked installation guide. Use DeepSeek TUI names only when matching an older release or diagnosing a legacy machine.
Can an existing DeepSeek TUI setup keep working?
Possibly. First identify its version, command, config directory, and active key source. Migrate deliberately instead of combining old and new snippets.
Where are installation and API-key steps?
They belong to the paired DeepSeek TUI installation guide, which uses current commands and keeps legacy names inside migration and troubleshooting sections.