Hellyeah

Troubleshooting

Common CLI, agent, billing, and tracking fixes.

hellyeah: command not found

You haven't run the install bootstrap yet, or the install directory isn't on your shell's PATH. Run:

curl -fsSL https://hellyeah.sh | sh

The output tells you which directory contains the installed binary (by default ~/.hellyeah/bin). If the installer printed an export line because it could not update your PATH automatically, run it:

export PATH="$HOME/.hellyeah/bin:$PATH"

Otherwise reload your shell:

exec $SHELL
hellyeah --help

On Windows, use a new terminal after installing:

powershell -NoProfile -ExecutionPolicy Bypass -Command "irm https://hellyeah.sh/install.ps1 | iex"
hellyeah --help

If another binary is shadowing the installed one:

where.exe hellyeah

The Hellyeah install path should appear before any older hellyeah.exe.

Install fails or fetch is slow

The installer downloads a native binary from https://releases.hellyeahai.com/cli and verifies it against checksums.txt. If the network drops, retry:

curl -fsSL https://hellyeah.sh | sh

If you already have Node/npm and need the npm fallback:

npm exec --yes --package hellyeah@latest -- hellyeah install

If the installer cannot write to its target directory, choose a writable prefix:

curl -fsSL https://hellyeah.sh | HELLYEAH_INSTALL_DIR="$HOME/.local" sh

On Windows:

$env:HELLYEAH_INSTALL_DIR="$HOME\Programs\Hellyeah"
powershell -NoProfile -ExecutionPolicy Bypass -Command "irm https://hellyeah.sh/install.ps1 | iex"

Windows binaries are initially unsigned. SmartScreen or Defender may warn on first run; inspect https://hellyeah.sh/install.ps1 and the release checksums.txt if your environment requires an audit trail.

To uninstall a Windows standalone install:

Remove-Item -Recurse -Force "$env:LOCALAPPDATA\Programs\Hellyeah"

Then remove %LOCALAPPDATA%\Programs\Hellyeah\bin from your user PATH.

On Alpine or another minimal musl system, install the C++ runtime first if the installer says the downloaded binary cannot start:

apk add libstdc++ libgcc

Auth looks stale

Check the current account:

hellyeah auth whoami

If it is wrong, sign out and sign in again:

hellyeah auth logout
hellyeah auth login

The agent does not know Hellyeah commands

Install or reinstall the skill:

hellyeah skills add hellyeah --global --yes

Then restart the agent session so it reloads local skills.

Launch fails because the wallet is low

Top up the prepaid wallet, then rerun the launch:

hellyeah wallet topup --amount 50
hellyeah wallet balance

Wallet top-ups open Stripe Checkout in your browser. Your agent cannot enter card details or add funds on its own.

Tracking is not linked

Create or inspect the org tracker:

hellyeah tracker state --json
hellyeah tracker create --domain <host> --json

If you do not have a production domain yet, use hellyeah tracker create --pre-launch --json, then update the same tracker with hellyeah tracker update --domain <host> when you launch.

Install the SDK with Tracking or the Install the SDK guide.

Report a bug

Send feedback from the CLI:

hellyeah feedback "what happened"

The positional message is filed as kind: "note". For structured agent reports (crashes, suggestions), pipe JSON to hellyeah feedback — see the reference.

On this page