@hyperscale0/cli 1.0.385 → 1.0.386

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/AGENTS.md +9 -4
  2. package/hyperscale.js +170 -170
  3. package/package.json +2 -2
package/AGENTS.md CHANGED
@@ -47,21 +47,26 @@ The login creates a named agent member with its own CLI grant. In sandbox
47
47
  it acts as the founder, `--on-behalf-of` included; `whoami` shows the
48
48
  founder's team role. The grant ends after 30 days, or 7 days unused, and so do
49
49
  sandbox keys `key create --name <name>` makes from it. `doctor` names where the
50
- token is stored. Access
51
- tokens last ten minutes; the CLI rotates the refresh token and keeps both in
50
+ token is stored. The
51
+ login's access token lasts an hour and ends with `device_login_expired`; the
52
+ CLI rotates the refresh token and keeps both in
52
53
  Keychain or a mode 0600 file. Logout removes them locally. Revoke the member or
53
54
  grant in the browser; `--revoke` only revokes a human PAT. Sandbox work within
54
55
  the grant runs directly. A live action exits 3 with `agent_approval_required`
55
56
  and a browser link; a human approves it with their password. A grant with
56
57
  money caps runs live calls inside them; a call over a cap exits 3 with
57
- `agent_cap_exceeded` and the same link. The CLI cannot approve its own work.
58
+ `agent_cap_exceeded`, the same link and a `cliCommand`. The founder decides
59
+ either from the browser or with `agent approvals approve|decline <id>`, whose
60
+ approve asks for the password; an agent token cannot call either.
58
61
 
59
62
  `agent setup [claude-code|codex|cursor]` uses the founder's CLI login to mint
60
63
  a named, sandbox-only agent credential (`agent_grant.create`). It keeps the
61
64
  token in the login's store, writes the host's MCP entry with
62
65
  `HYPERSCALE_TOKEN` as the bearer variable, and installs the skill into the
63
66
  host's skills folder. `--name` names the agent member, so two projects can
64
- each keep their own. `agent token [host] [--name <name>] [--dir <path>]`
67
+ each keep their own. A rerun keeps a working stored token and changes the
68
+ grant in place; `--rotate` mints a new one. `agent caps` changes the money
69
+ caps through `agent_grant.caps.set` and keeps the token. `agent token [host] [--name <name>] [--dir <path>]`
65
70
  prints the stored token so the shell can export it as `HYPERSCALE_TOKEN`; MCP
66
71
  and the CLI then use the same door. With no `--name`, it reads the agent set
67
72
  up for the directory, then the host's default name.