Install

Three steps from zero to "ask your agent to launch ads." The first run uses npx to fetch and install the CLI; every command after that runs as a bare hellyeah.

1. Install the CLI

npx hellyeah install

This fetches the hellyeah package, installs the matching binary for your platform, and puts hellyeah on your PATH. After it finishes you can call hellyeah directly, with no npx prefix.

Verify:

hellyeah --help

If hellyeah is not found, your shell's PATH may need a reload (exec $SHELL), or you may need to add the install directory printed during step 1 to your shell profile.

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. Install the agent skill

hellyeah skills add hellyeah

This teaches your coding agent when to call which command, how to chain them, and where to pause for human approval. The skill is installed into your agent's local skill directory.

Target a specific agent with --agent:

hellyeah skills add hellyeah --agent claude-code
hellyeah skills add hellyeah --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.

Install the Hellyeah CLI on this machine.

1. Run `npx hellyeah install` and 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. Run `hellyeah skills add hellyeah` 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):

1. Environment variables: HELLYEAH_API_URL, HELLYEAH_AUTH_PUBLISHABLE_KEY, HELLYEAH_AUTH_CLIENT_ID
2. Config file: ~/.config/hellyeah/config.json
3. 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.