What Is DeepSeek TUI? CodeWhale Rename Explained

Questions this page should answer fast

What kind of product category does DeepSeek TUI really belong to?
Why do users keep searching for install, config, modes, comparisons, and rename explainers right after they discover the name?
Which branch should a new reader open first after understanding the product at a high level?

What this page should help you decide

This page should help the reader classify DeepSeek TUI correctly, understand that the current upstream name is CodeWhale, and choose the right next branch without guessing.

Fast diagnosis

Rename confusion

If someone does not realize DeepSeek TUI and CodeWhale are the same project lineage, the rest of the install and command guidance will feel contradictory.

Category confusion

If someone still thinks the product is only a terminal chat shell, they will miss why files, shell actions, approval flows, and config pages matter so much.

Workflow confusion

If the user understands it as a coding-agent workflow, the surrounding branches become easier to navigate because each branch answers a different operational question.

Next-step confusion

A new reader usually does not need every branch at once. They need the one that matches their current question: install, config, docs, modes, or comparison.

Step-by-step workflow

Start from the rename first
Explain that DeepSeek TUI is the old search term while CodeWhale is the current upstream product name.
Then explain the operating shape
Describe the tool as a terminal agent that works across prompts, files, shell commands, config, and structured workflows rather than as a thin chat layer.
Map the core branches to real questions
Install answers how to get started, Config answers how to connect and tune it, Docs answer what the upstream project formally says, and Modes answer how the work style changes.
Choose the next page by actual need
A new user who cannot run the binary should go to Install. A user who installed it but cannot connect should go to Config. A user comparing tools should go to Comparisons.
Leave once the category is clear
This page should narrow the product definition and send the reader into the correct operational branch, not keep them at the overview layer forever.

Common mistakes

Treating DeepSeek TUI and CodeWhale as different products instead of a rename transition.
Treating DeepSeek TUI as just another terminal chatbot and missing the coding-agent workflow around it.
Opening docs, modes, or MCP pages before basic install and config questions are settled.
Reading this page as if it should replace the deeper branches instead of choosing the right one.

When to leave this page

Leave this page once you can explain what DeepSeek TUI is, why the current upstream name is CodeWhale, and whether your next stop should be install, config, docs, modes, or comparisons.

Use-it-now examples

Start from working examples first, then adjust the details.

Describe the product in one operational sentence

A useful first sentence usually mentions terminal work, files, shell actions, config, and structured agent behavior.

# write one sentence that explains terminal agent workflow, not just 'AI chat'

Choose the next branch by the current blocker

Once the category is clear, route immediately to install, config, docs, or comparisons based on the user's actual question.

# if binary missing -> install
# if auth broken -> config
# if evaluating fit -> comparisons

Common failure branches

Work out which layer failed first instead of treating every problem as the same.

The site still feels fragmented after reading this page

That usually means the product is still being framed as terminal chat instead of a coding-agent workflow.

A new reader jumps straight into deep docs and gets lost

They probably needed install or config first. Route by blocker, not by curiosity alone.