Skip to content
Documentation
Troubleshooting
Install

Install

Common issues when installing Valdr via Homebrew or verifying the CLI after install.

valdr: command not found after install

Symptom: Homebrew installation succeeds but valdr version returns command not found.

Likely cause: Your shell’s PATH does not include Homebrew’s bin directory, or the shell has not reloaded since install.

Fix:

brew --prefix
echo "$PATH"
command -v brew
command -v valdr

# Reload your shell config if needed
source ~/.zshrc   # or ~/.bashrc

Homebrew usually installs to /opt/homebrew/bin on Apple Silicon and /home/linuxbrew/.linuxbrew/bin on Linux. If command -v valdr is still empty after reloading, follow Homebrew’s post-install instructions to add it to your PATH, then open a new terminal window and try again.

brew install valdr fails with tap not found

Symptom: Homebrew says the valdr formula does not exist.

Likely cause: The Valdr tap was not added first.

Fix:

brew tap projectviking-ai/valdr https://github.com/projectviking-ai/homebrew-valdr.git
brew install valdr

Wrong architecture

Symptom: valdr version returns an architecture mismatch error.

Likely cause: You are running a binary built for a different CPU architecture.

Fix:

uname -m
brew reinstall valdr
  • arm64 on macOS uses the macOS arm64 package.
  • x86_64 on Linux uses the Linux x64 archive.
  • aarch64 or arm64 on Linux uses the Linux arm64 archive.

Permission denied running valdr

Symptom: Running a copied or extracted valdr binary returns permission denied.

Likely cause: The file is not marked executable.

Fix:

chmod +x ./valdr

If you installed with Homebrew, prefer the brewed binary returned by command -v valdr. Reinstalling with Homebrew is usually the quickest fix.

Related

License