@hyperscale0/cli 1.0.382 → 1.0.384

package/AGENTS.md

@@ -31,20 +31,19 @@ and product IDs come from the login and the selected product. Lists accept
 pass `--idempotency-key` to retry safely. Without a TTY a missing required flag
 exits 2 and names the flag.
 
-Check `hyperscale whoami --json` first. To sign in a founder who has an
-account, pipe their password on stdin to `auth login --email <email> --json`;
-it mails a six-digit code and exits. Ask the founder for the code, then run
-`auth login --code <code> --json`. To approve in a browser instead, run
+Check `hyperscale whoami --json` first. To sign in a founder, run
 `auth login --no-open --json`: the first stdout line is `approval_needed` with
-the code and URL, and the last is `signed_in`. Rerun to resume a pending login.
-For CI, pipe a `hyperscale_pat_` token to `auth login --with-token`. To create an account, pipe the
-founder's password on stdin to `auth signup --email <email> --name <name>
---company <company> --json`; it mails a six-digit code and exits. Ask the
-founder for the code, then run `auth signup --code <code> --json`. The account
-starts in sandbox. `auth verify` confirms an existing account's email the same
-way. Do not print or persist credentials in project files.
-
-Either login creates a named agent member with its own CLI grant. In sandbox
+the code and URL, and the last is `signed_in`. Hand the founder the URL; a
+founder without an account creates one on the same page, in sandbox. Rerun to
+resume a pending login. To sign a founder up without a browser, pipe the
+password to `auth signup --name <name> --email <email> --company <company>
+--json` (stdout `code_sent`), then pipe the same password to `auth signup --email <email>
+--code <code> --json` with the code the person reads from that mailbox
+(stdout `signed_in`). For CI, pipe a `hyperscale_pat_` token to
+`auth login --with-token`. Do not print or persist credentials in project
+files.
+
+The login creates a named agent member with its own CLI grant. In sandbox
 it acts as the founder, `--on-behalf-of` included; `whoami` shows the
 founder's team role. The grant ends after 30 days, or 7 days unused, and so do
 sandbox keys `key create --name <name>` makes from it. `doctor` names where the
@@ -53,8 +52,9 @@ tokens last ten minutes; the CLI rotates the refresh token and keeps both in
 Keychain or a mode 0600 file. Logout removes them locally. Revoke the member or
 grant in the browser; `--revoke` only revokes a human PAT. Sandbox work within
 the grant runs directly. A live action exits 3 with `agent_approval_required`
-and a browser link; a human approves it with their password. The CLI cannot
-approve its own work.
+and a browser link; a human approves it with their password. A grant with
+money caps runs live calls inside them; a call over a cap exits 3 with
+`agent_cap_exceeded` and the same link. The CLI cannot approve its own work.
 
 `agent setup [claude-code|codex|cursor]` uses the founder's CLI login to mint
 a named, sandbox-only agent credential (`agent_grant.create`). It keeps the

package/README.md

@@ -14,13 +14,12 @@ hyperscale auth login
 
 ## Sign in
 
-| Situation            | Command                                                                |
-| -------------------- | ---------------------------------------------------------------------- |
-| A browser is at hand | `hyperscale auth login`, then approve the code it shows                |
-| No browser           | `hyperscale auth login --email you@example.com`, then the emailed code |
-| No account yet       | `hyperscale auth signup`                                               |
-| CI                   | Pipe a personal access token to `hyperscale auth login --with-token`   |
-| A coding agent       | `hyperscale agent setup claude-code` (or `codex`, `cursor`)            |
+| Situation        | Command                                                              |
+| ---------------- | -------------------------------------------------------------------- |
+| Signed in or new | `hyperscale auth login`, then approve the code in the browser        |
+| New, no browser  | `hyperscale auth signup --name --email --company`, then the code     |
+| CI               | Pipe a personal access token to `hyperscale auth login --with-token` |
+| A coding agent   | `hyperscale agent setup claude-code` (or `codex`, `cursor`)          |
 
 `hyperscale whoami` shows who is signed in and when the login ends: after 30
 days, or 7 days unused. `hyperscale auth logout --revoke` signs out and revokes
@@ -39,7 +38,7 @@ hyperscale scenario run day.json
 `product.configuration.json`, writes a first scenario and links the folder in
 `hyperscale.json`. Inside it every command uses that Product, and `hsx check`,
 `plan` and `apply` need no file arguments. `link` links an existing `.hsx` file
-instead. `--template storefront` also writes a Vite React shop.
+instead.
 
 No Product yet? `hyperscale architect chat --brief "<your business>" --yes`
 drafts, checks and saves one, or write HSX and run