Claude Skills Guide

Claude Code Command Not Found After Install: Troubleshooting Guide

Installing Claude Code should give you immediate access to the claude CLI tool. Instead, you’re staring at zsh: command not found: claude. This happens more often than you’d think, and the fix is usually straightforward.

This guide walks through the most common causes and their solutions, so you can get back to coding with Claude’s AI assistance.

Understanding the Problem

When you install Claude Code, the installer adds the Claude CLI to a specific directory on your system. Your shell needs to know where to find that executable. If the installation directory isn’t in your PATH environment variable, your terminal simply cannot locate the claude command.

The error message might appear as:

zsh: command not found: claude

or

bash: claude: command not found

The root cause is almost always PATH-related, but there are a few other possibilities worth checking.

Solution 1: Verify the Installation Location

First, confirm where Claude Code was actually installed. Run this command to search for the executable:

sudo find /usr -name "claude" -type f 2>/dev/null
sudo find /usr/local -name "claude" -type f 2>/dev/null
sudo find "$HOME" -name "claude" -type f 2>/dev/null

On macOS, the installer typically places the CLI in /usr/local/bin/ or ~/.local/bin/. On Linux systems, it might go to /usr/bin/ or a user-local directory.

Once you locate the executable, note the full path. You’ll need it for the next steps.

Solution 2: Check Your PATH Configuration

Your shell searches for commands in directories listed in the PATH environment variable. Let’s verify what’s currently in your PATH:

echo $PATH

If the directory containing the Claude executable isn’t listed, you need to add it. Open your shell configuration file:

For Zsh (macOS default):

nano ~/.zshrc

For Bash:

nano ~/.bashrc

Add this line to the end of the file, replacing /usr/local/bin with the actual path where Claude is installed:

export PATH="/usr/local/bin:$PATH"

Save the file and reload your shell configuration:

source ~/.zshrc   # for Zsh
source ~/.bashrc  # for Bash

Now try running claude again:

claude --version

Solution 3: Fix Shell Initialization Issues

Sometimes the PATH is correct in login shells but not in interactive non-login shells. This commonly happens on macOS when using Terminal or iTerm2.

The installer typically adds a snippet to your shell config that handles this. Check if the following appears in your ~/.zshrc:

# Claude Code installer
if [ -f "/usr/local/bin/claude" ]; then
    export CLAUDE_PATH="/usr/local/bin/claude"
fi

If the installer snippet is missing or corrupted, manually add it. Alternatively, some users find success by placing PATH exports at the very top of their shell config, before any conditional logic or framework initializations.

The Claude installer may create a symbolic link rather than copying the binary directly. Verify the symlink exists and points to a valid target:

ls -la /usr/local/bin/claude

If you see something like claude -> ../Cellar/claude/..., verify the target exists. Broken symlinks are a common cause of this error. Recreate the symlink if needed:

sudo ln -sf /path/to/actual/claude /usr/local/bin/claude

Solution 5: Reinstall Claude Code

If the above solutions don’t work, the installation may be corrupted or incomplete. Reinstalling is often faster than debugging further.

Uninstall the current installation:

sudo rm -f /usr/local/bin/claude
sudo rm -rf ~/.claude

Then reinstall using the official installer:

curl -sSL https://raw.githubusercontent.com/anthropics/claude-cli/main/install.sh | sh

Or download the latest release from the official repository and follow the installation instructions specific to your operating system.

Solution 6: Verify Permissions

Permission issues can prevent the shell from executing the Claude binary. Check the file permissions:

ls -la /usr/local/bin/claude

The file should have execute permissions (look for x in the permissions string). If it doesn’t, fix it:

sudo chmod +x /usr/local/bin/claude

Also ensure your user has read access to the file and its parent directories.

Using Claude Skills Once Working

Once you resolve the command not found error, you’ll have access to Claude’s full ecosystem. Best Claude Code skills to install first covers which skills are worth adding immediately. Skills extend Claude’s capabilities for specialized tasks. The frontend-design skill helps generate UI components and layouts. The pdf skill enables document manipulation and extraction. The tdd skill assists with test-driven development workflows.

Other valuable skills include supermemory for managing project context across sessions, docx for Word document automation, and xlsx for spreadsheet operations. Skills are .md files stored in ~/.claude/skills/ — place the skill file there to activate it.

Prevention Tips

To avoid this issue in the future, keep these tips in mind:

  1. Restart your terminal after installing CLI tools to ensure shell initialization completes properly
  2. Use explicit paths when debugging: /usr/local/bin/claude --version confirms the binary works even if PATH is broken
  3. Check shell framework configs if you use Oh My Zsh or similar frameworks—they may override PATH settings

Wrapping Up

The “claude: command not found” error almost always comes down to PATH configuration. By locating the executable, adding its directory to PATH, and verifying permissions, you can resolve this in under five minutes.

If you continue experiencing issues after trying these solutions, check the official Claude Code documentation or open an issue on the GitHub repository with details about your operating system and installation method.

Built by theluckystrike — More at zovo.one

Explore Our Developer Guides

© 2026 theluckystrike Developer Guides