Homebrew command not found usually means brew installed the package but your shell still does not expose the brew-owned binary

This variant deserves its own page because Homebrew users often trust the package install step but forget that terminal sessions still need the correct Homebrew path exported and prioritized.

Site detail pageDeepSeek TUI Homebrew Command Not FoundTroubleshooting

Questions this page should answer fast

Did brew install into a directory your shell exports?
Is another package path shadowing the brew binary?
Did you verify the command in a truly fresh terminal session?

What this page should help you decide

This page should help the reader isolate brew-path exposure, shell profile ordering, and binary shadowing by other package routes.

Fast diagnosis

Brew location

Check whether the package lives under the Homebrew prefix your machine actually uses.

Shell export

Make sure your shell profile exports that Homebrew bin location for the terminal you really use.

Shadowing

Look for an older npm, cargo, or manual binary that still resolves earlier than the brew path.

Step-by-step workflow

Confirm the brew install really exists
Verify the package is present before assuming the install itself failed.
Inspect the active shell path
Check whether the Homebrew bin path is exported and whether it appears early enough to win resolution.
Retest after a new terminal session
A path fix that only exists in one shell window is not a real fix yet.
Remove or deprioritize competing routes
If another package path resolves first, the brew install may be correct but effectively invisible.

Common mistakes

Re-running `brew install` when the real issue is shell path export.
Assuming every terminal profile on macOS reads the same startup files.
Leaving another package manager's binary earlier in PATH and blaming Homebrew.

When to leave this page

Leave this page once the brew-owned binary resolves first in the shell you actually use every day.

Use-it-now examples

Start from working examples first, then adjust the details.

Verify brew package presence before changing PATH

Confirm the package exists in Homebrew first, then inspect whether the active shell exports the right brew prefix.

brew list | rg deepseek-tui || true
command -v codewhale || which codewhale

Retest after a full new terminal launch

A brew path fix should survive a fresh terminal profile, not just the current shell window.

command -v codewhale || which codewhale
# quit and relaunch terminal, then repeat

Common failure branches

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

Brew knows the package but the shell does not

That is a path-export problem first, not a package-install problem.

The brew path exists but another binary still wins

Look for shadowing by npm, cargo, or a manual binary before you blame Homebrew.