Cloud CLI reference

These commands ship in @hogsend/cli, which is a dependency of every scaffolded app. Run them through your package manager from inside the app:

pnpm hogsend publish      # pnpm / yarn
npx hogsend publish       # npm
bunx hogsend publish      # bun

Every command takes --cloud <url> (default: HOGSEND_CLOUD_URL, else https://cloud.hogsend.com) and --json.

Signing in

hogsend signup

Create an account from this machine, or sign in to an existing one. A brand-new address gets an account, an organization and a production environment; an address that already has one is simply signed in.

hogsend signup
hogsend signup --email me@acme.com --org "Acme Rockets"
echo 123456 | hogsend signup --email me@acme.com --json

Nothing is provisioned until your first hogsend publish, so signing up costs nothing and takes seconds.

hogsend login

The browser device flow. Prints a short code and a URL, and opens your browser at the approval page with the code prefilled. The printed code and URL always work on their own, so a machine with no browser completes the same flow by hand.

hogsend login
hogsend login --email me@acme.com
hogsend login --cloud https://cloud.acme.internal
hogsend login --label ci-runner --no-browser

With --email, no browser is involved at all: a six-digit code is mailed to that address and typed back. If the address has no account yet it gets one, exactly as hogsend signup would.

--org is not accepted here. A second organization is a decision, not a flag on a login — use hogsend signup --org when you have no organization yet.

hogsend whoami

hogsend whoami
hogsend whoami --json

Asks the cloud rather than reading the local file, so a session that was revoked from the dashboard reports as signed out — which is the question this command is actually being asked.

hogsend logout

hogsend logout

The revoke is attempted first so the token stops working everywhere, not just here — but the local entry is deleted either way. A cloud that is unreachable, or a session already revoked from the dashboard, must never leave a token on disk that you believe you removed.

Deploying

hogsend publish

hogsend publish
hogsend publish --env staging
hogsend publish --allow-upgrade

What gets uploaded. Everything your repository ignores is left out, and .git, node_modules, dist and every .env* are excluded unconditionally, whatever .gitignore says — including a .gitignore that tries to re-include them with a negation.

The engine version comes from your lockfile, not from a flag. If it disagrees with what the target stack is running, the cloud refuses the deploy unless you pass --allow-upgrade.

With no session, hogsend publish on a terminal offers to sign you in and then continues the same publish. Headless, it refuses with the commands to run.

--no-wait prints the build id and exits 0 straight after the upload, whether or not stdout is a terminal.

hogsend open

hogsend open
hogsend open --env staging

The URL is always printed, whether or not a browser could be opened, so this works over SSH and in CI.

hogsend env pull

hogsend env pull
hogsend env pull --env staging --force

Merges HOGSEND_API_URL and HOGSEND_API_KEY into the .env beside your app — it never rewrites the file. Existing variables, comments and ordering survive, and a key already set to a different value is reported and refused rather than clobbered.

The key is never printed. You are told that it was written and where, never what it is, because CLI output lands in scrollback, CI logs and screen shares.

Refusal catalog

Every one of these is what the CLI actually prints. The second line is the hint it prints under the message.

Sign-in

A code is good for ten minutes and survives two wrong attempts; the third kills it. An interactive run re-prompts once before giving up, so a deliberate re-run always has budget left.

Session

On a terminal the last two are an offer, not a refusal: the publish signs you in and carries on.

Publish

Headless and agent patterns

Every command takes --json and emits exactly one JSON document on stdout. Human-facing lines go to stderr in that mode, so the document is always parseable.

Sign in unattended — the code arrives by email and goes in on stdin:

echo 123456 | hogsend signup --email you@example.com --json

Publish without watching, then poll separately:

hogsend publish --no-wait --json

Never prompts without a terminal. Every question a headless run would have asked becomes a non-zero exit and a printed command instead. A CI job cannot hang on a hidden prompt.

The session token is never printed — not by any command, not in any --json result. It exists in ~/.hogsend/credentials.json (mode 0600) and nowhere else.

For driving all of this from an agent without shelling out, see Agents & MCP.