DeepSeek TUI Homebrew command not found usually means brew installed the package but your shell still does not see it

This version of the error deserves its own page because Homebrew users often assume the brew install step automatically solves shell discovery across every terminal session.

Why the Homebrew variant is different

The generic command-not-found page covers npm and cargo too. This page exists because Homebrew introduces its own path expectations, machine-level package assumptions, and shell profile quirks.

What to verify first

Did Homebrew install the package into a location your shell exports?
Did you open a new terminal after install?
Are you mixing brew expectations with a different install route?