Troubleshooting

Solutions for common issues with Harper.

Symptom

Harper is running an older version than expected or displaying an outdated UI.

Cause

This typically occurs when:

A new version was released but the local binary was not updated
Multiple installations of Harper exist (e.g., via Homebrew, manual build, or in different directories)
The binary in PATH is pointing to an older build

Resolution

Option 1: Rebuild from source

If you have the source code:

# Pull the latest changes
git pull origin main

# Build the project
cargo build --release

# Verify the version
./target/release/harper --version

Option 2: Update local binary

Copy the newly built binary to the bin directory:

cp target/release/harper bin/harper

Option 3: Update system binary

Copy the binary to your system's local bin directory:

# Common locations:
cp target/release/harper ~/.local/bin/harper

# Or use Homebrew's prefix:
cp target/release/harper $(brew --prefix)/bin/harper

Option 4: Via Homebrew

If you installed Harper via Homebrew:

brew upgrade harpertoken/tap/harper-ai

Verification

Check which binary is being used

which harper

Check the version

harper --version

Compare with latest release

Check the latest release on GitHub: https://github.com/harpertoken/harper/releases

Multiple installations

If you have multiple installations, you may see unexpected behavior. To check locations:

# Find all harper binaries
find /usr/local/bin -name "harper" 2>/dev/null
find ~/.local/bin -name "harper" 2>/dev/null
find $HOME -name "harper" 2>/dev/null

Ensure the PATH points to the desired installation.