Install

Install once. Then ask your agent to launch ads.

1. Install the CLI

Pick your platform or package manager. The native installer (curl / PowerShell) is recommended: it downloads the matching native binary, verifies its checksum, and puts hellyeah on your PATH with no Node required. npm and npx are alternatives for environments already standardized on Node.

Recommended · macOS & Linux · no Node required.

curl -fsSL https://hellyeah.sh/install.sh | sh -s -- --agents -y

Installs Hellyeah and the agent skills.

Recommended · PowerShell · no Node required.

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

Installs to %LOCALAPPDATA%\Programs\Hellyeah\bin\hellyeah.exe and updates your user PATH.

Prefer to review the script before running it? Download, inspect, then run:

irm https://hellyeah.sh/install.ps1 -OutFile install.ps1
notepad .\install.ps1
powershell -NoProfile -ExecutionPolicy Bypass -File .\install.ps1

Alternative · requires Node · installs the hellyeah wrapper globally onto your PATH.

npm i -g hellyeah@latest

Alternative · requires Node · resolves the latest version, then runs the bundled installer.

npx hellyeah@latest install

Custom install location

The native installer writes to a default prefix. Point it somewhere writable when you need to:

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

That writes the Unix binary to $HOME/.local/bin/hellyeah. On Windows:

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

Verify

hellyeah --help

If the installer printed an export line because it could not update your PATH automatically, run it now. For example:

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

Otherwise reload your shell with exec $SHELL (or open a new terminal; on Windows, always open a new terminal). The exact directory to add is the one printed during step 1.

Update later with:

hellyeah update

Standalone installs re-run the verified installer into the same directory, so this also repairs a stale binary in place. On Windows, the replacement is scheduled after the current hellyeah.exe process exits.

2. Log in

hellyeah auth login

This opens your browser to the Hellyeah sign-in page. After you authenticate, the CLI stores credentials under ~/.config/hellyeah/ and refreshes them as needed. First-time login auto-creates a Hellyeah account.

Verify:

hellyeah auth whoami

3. Connect your agent

The curl install command already installs the skills. If you used Windows, npm, npx, or skipped --agents, run:

hellyeah skills add hellyeah --global --yes

Target a specific agent with --agent:

hellyeah skills add hellyeah --global --agent claude-code
hellyeah skills add hellyeah --global --agent cursor

Done

Your coding agent now knows how to use the CLI. Ask it:

"launch ads for my landing page"

and it takes over: researches your business, generates creatives, drafts a campaign, asks you to confirm funding and launch. Walk through it end to end in Launch your first ad.

Prompt for your agent

Paste this into Claude Code, Cursor, or any agent that runs shell commands to bootstrap a fresh machine:

Install the Hellyeah CLI on this machine.

1. Install Hellyeah for this OS: on macOS/Linux run `curl -fsSL https://hellyeah.sh/install.sh | sh -s -- --agents -y`; on Windows run `powershell -NoProfile -ExecutionPolicy Bypass -Command "irm https://hellyeah.sh/install.ps1 | iex"` and then `hellyeah skills add hellyeah --global --yes`. Confirm `hellyeah --help` works afterwards. If the binary isn't found, tell me which directory to add to PATH.
2. Run `hellyeah auth login` and wait for the browser flow to finish, then verify with `hellyeah auth whoami`.
3. Make sure the Hellyeah skill is installed so you (the agent) know how to drive the CLI.
4. Print a one-line confirmation with my account email and the installed CLI version.

Do not launch any campaigns yet.

Environment & config

Most users won't need this section. Use it only when Hellyeah support asks you to inspect or override the CLI connection settings.

Resolution order (first match wins per field):

Environment variables: HELLYEAH_API_URL, HELLYEAH_AUTH_PUBLISHABLE_KEY, HELLYEAH_AUTH_CLIENT_ID
Config file: ~/.config/hellyeah/config.json
Production defaults baked into the release binary

Config file example (~/.config/hellyeah/config.json):

{
  "apiUrl": "https://api.hellyeahai.com",
  "authPublishableKey": "pk_...",
  "authClientId": "cli_..."
}

Inspect resolved config:

hellyeah config status

Prints the resolved API URL, auth settings, config file path, and credential state as JSON.