zsh command not found mac terminal fix: step by step for macOS 10.15 and later

What the zsh command not found message means

The message has two parts. The word before the first colon names the shell that ran your command. The word after names the command that shell could not find. So zsh: command not found: brew means you are in zsh, and zsh searched for a program called brew.

That search uses your PATH. Run echo $PATH in Terminal to see the folders zsh checks, separated by colons. If the program sits in a folder that is not on that list, zsh acts as if the program does not exist. Common causes are that gap and a simple typo.

Why old bash tutorials break on a Mac

Apple made zsh the default shell starting with macOS 10.15. Before that, bash was the default in macOS 10.14 and earlier. Tutorials written in those years often say to add a line to ~/.bash_profile. zsh does not read that file for your Terminal sessions, so the line does nothing.

Apple describes the zsh startup files this way. .zprofile runs at login, including over SSH, and is the counterpart to .bash_profile. .zshrc runs for each new Terminal session and is the counterpart to .bashrc. Apple's description points to .zprofile for login setup, which is where Homebrew's setup line usually goes.

Match the message to its likely cause

Work through the checks in order

1. Read the word before the colon. zsh means you are in zsh. bash means you are in bash.
2. Check whether the program exists with command -v name. No output means zsh cannot find it.
3. If the program exists, find its folder. For Homebrew on Apple silicon, that is /opt/homebrew/bin.
4. Check that the folder is on PATH with echo $PATH. If it is missing, add it in ~/.zprofile.
5. Open a new Terminal window and run the failed command again.

A worked example with Homebrew on Apple silicon

Say you ran brew install wget and saw zsh: command not found: brew. A tutorial told you Homebrew was already installed. Start by checking the file itself. Run ls /opt/homebrew/bin/brew in Terminal.

If the path prints, Homebrew is installed and only PATH is missing. Open the startup file with nano ~/.zprofile. Add eval "$(/opt/homebrew/bin/brew shellenv)" on its own line. Save with ⌃ O and Return, then exit with ⌃ X. Open a new window and run brew --version. A version number means the fix worked.

If ls says No such file or directory, the install never finished. Install Homebrew again from the official Installation page at docs.brew.sh. Two details trip people up. The line must match your Mac, and it should appear only once. Run cat ~/.zprofile before you edit, so you see what is already there.

Set zsh as the shell, or confirm the one you have

Apple says to change the login shell with chsh -s, followed by a path listed in /etc/shells. For zsh, use /bin/zsh. On macOS 13 or later, you can also open System Settings > Users & Groups > Advanced Options and set the Login shell there. This changes the account default, so use it when you want zsh everywhere.

Terminal can also open its own shell. Choose Terminal > Settings > General. Next to Shells open with, select Command (complete path), then enter /bin/zsh. Apple notes that this changes Terminal's shell without changing the system default. That makes it a safe test for a single app.

To see which shell runs in the current window, run echo $0. To see the login shell set for your account, run echo $SHELL. The two can differ. Use $0 when you want to know what you are typing into right now.

Mistakes that bring the error back

• Adding the same eval line twice. The file gets messy, and it is hard to tell which line is live. Run cat ~/.zprofile before you edit.
• Editing ~/.bash_profile while you use zsh. zsh does not read it, so nothing changes.
• Testing in the old window. That window keeps its old PATH. Open a new window, or run exec zsh, before you judge the fix.
• Pasting sudo commands from an unknown site. Read each command first. Skip any that change system folders without a reason you understand.
• Stopping after one lucky result. Run command -v and brew --version in a new window, then run the command that failed.

Intel Macs, version managers, and editor terminals

The default Homebrew folder on Apple silicon is /opt/homebrew. Intel Macs may use a different folder, so do not copy that line without checking. Run ls on the path your installer names, or read the output the installer printed. That output is written for your machine.

Tools installed through a version manager often need a setup line too. Add that line to the zsh file the tool names in its install output. If a tool works in one window and fails in another, compare the two windows with echo $0 first. Different shells read different files.

Editors have their own terminals. An integrated terminal in Cursor or VS Code may run a different shell or read different settings than Terminal. If the error appears only in the editor, check that editor's terminal settings. VS Code for developers on Mac covers terminal setup in more depth.

Where Lazur helps, and where it does not

Lazur is a voice assistant for the Mac. Hold ⌥ ⌘ to ask about anything on screen, and Lazur answers out loud. With the Terminal error on screen, ask what the message means. Ask where a setting lives, and Lazur draws a circle and a label around it.

Lazur does not run commands for you. It does not click buttons or edit files. You type or paste each command, and you read it before you press Return. Hold fn to dictate text at the cursor when you write a note to a teammate. Dictated commands need the same check as typed ones.

Lazur listens and looks only while you hold the shortcut. Audio and the screenshot go to AI providers to answer, and they are not stored. If your Terminal shows client or patient data, follow your employer's rules before you ask Lazur about it.

Keep the fix from coming back

Write down the file you changed, the line you added, and the date. Keep that note with your project or your dotfiles, so the next setup starts from a known state. When you move to a new Mac, read the file before you copy it. Check that each path still exists on the new machine.

When the message is not about zsh

Some errors look similar but mean something else. zsh: permission denied: ./script.sh means the file exists, but you cannot run it. zsh: no such file or directory means the path you typed is wrong. Use ls -l on the path to check its location and permissions. Keep the PATH fix for messages that say command not found.