@tryarcanist/cli 0.1.379 → 0.1.381

package/README.md

@@ -1,6 +1,6 @@
 # Arcanist CLI
 
-Command-line interface for [Arcanist](https://www.tryarcanist.com): follow session output and manage access tokens from your terminal or automation.
+Command-line interface for [Arcanist](https://www.tryarcanist.com): follow session output and manage environments from your terminal or automation.
 
 ## Install
 
@@ -13,34 +13,27 @@ Requires Node.js 22 or newer.
 ## Quick start
 
 ```bash
-arcanist auth login                 # approve login in your browser
+printf "arc_..." | arcanist auth login --token-stdin
 arcanist sessions list --json
 ```
 
 ```bash
-export ARCANIST_TOKEN=arc_...       # write-scoped for prepare, review, and stop
+export ARCANIST_TOKEN=arc_...       # write-scoped for prepare, review, and sandbox build
 SESSION_ID=$(arcanist sessions list --json | jq -r '.sessions[0].id')
 arcanist sessions events "$SESSION_ID" --follow --json
 ```
 
 ## Authentication
 
-Start browser authorization from the CLI:
+Mint a token in **Settings > CLI**, then pipe it to the CLI:
 
 ```bash
-arcanist auth login
-# approve the request in the browser
+printf "arc_..." | arcanist auth login --token-stdin
 ```
 
-Token config is stored at `~/.arcanist/config.json`. Existing automation can still provide a token through `ARCANIST_TOKEN` or `--token-stdin`. Multiple active tokens per user are supported; revoke tokens independently when a device or workflow no longer needs access.
-
-Use a read-scoped token for inspection and debugging; use a write-scoped token to prepare or retry environments, trigger a Zeus review, stop a session, or manage tokens.
-
-You can also pipe the token via stdin:
+Token config is stored at `~/.arcanist/config.json`. Existing automation can provide a token through `ARCANIST_TOKEN` or `--token`. Multiple active tokens per user are supported; revoke tokens independently when a device or workflow no longer needs access.
 
-```bash
-printf "arc_..." | arcanist auth login --token-stdin
-```
+Use a read-scoped token for inspection and debugging; use a write-scoped token to prepare or retry environments, trigger an Arcanist review, or build a sandbox layer.
 
 Auth and API URL precedence:
 
@@ -115,20 +108,20 @@ Exit codes:
 130 interrupted
 ```
 
-`tokens create` and `sandbox build` send an `Idempotency-Key` header. The CLI does not auto-retry those endpoints; retry explicitly with the same `--idempotency-key` when a request may have already reached the server. Both use auto-random keys by default, so only an explicit key makes cross-invocation retries safe.
+`sandbox build` sends an `Idempotency-Key` header. The CLI does not auto-retry that endpoint; retry explicitly with the same `--idempotency-key` when a request may have already reached the server. It uses auto-random keys by default, so only an explicit key makes cross-invocation retries safe.
 
 ## Commands
 
 ### `arcanist environments prepare`
 
-Prepare the current repository for Zeus. Pass `owner/repo` outside a checkout. A write-scoped token is required.
+Prepare the current repository for Arcanist. Pass `owner/repo` outside a checkout. A write-scoped token is required.
 
 ```bash
 arcanist environments prepare --wait --json
 arcanist environments prepare owner/repo --wait --poll-interval 5000 --json
 ```
 
-Agents should follow `repository.nextAction` and `repository.command`. Request a Zeus review only when `nextAction` is `review`. When `command` is `null`, do not invent an API call; surface `question` / `secretRequest` to a human. `--wait` waits through internal handoffs until setup is ready or there is a real action for the user or Arcanist.
+Agents should follow `repository.nextAction` and `repository.command`. Request an Arcanist review only when `nextAction` is `review`. When `command` is `null`, do not invent an API call; surface `question` / `secretRequest` to a human. `--wait` waits through internal handoffs until setup is ready or there is a real action for the user or Arcanist.
 
 ### `arcanist environments status`
 
@@ -139,7 +132,7 @@ arcanist environments status owner/repo --json
 arcanist environments status owner/repo --wait --poll-interval 5000 --json
 ```
 
-Agents should follow `repository.nextAction` and `repository.command`. Request a Zeus review only when `nextAction` is `review`. When `command` is `null`, do not invent an API call; surface `question` / `secretRequest` to a human. `--wait` waits through internal handoffs until setup is ready or there is a real action for the user or Arcanist.
+Agents should follow `repository.nextAction` and `repository.command`. Request an Arcanist review only when `nextAction` is `review`. When `command` is `null`, do not invent an API call; surface `question` / `secretRequest` to a human. `--wait` waits through internal handoffs until setup is ready or there is a real action for the user or Arcanist.
 
 ### `arcanist environments retry`
 
@@ -152,7 +145,7 @@ arcanist environments retry owner/repo --wait --poll-interval 5000 --json
 
 ### `arcanist environments login`
 
-Log into your app once in a throwaway local browser and save that login on the environment so Zeus sessions start signed in. Alias: `arcanist env login`. A write-scoped token is required. Pass an environment id or `owner/repo` outside a checkout; the environment must have an app runtime configured.
+Log into your app once in a throwaway local browser and save that login on the environment so Arcanist sessions start signed in. Alias: `arcanist env login`. A write-scoped token is required. Pass an environment id or `owner/repo` outside a checkout; the environment must have an app runtime configured.
 
 ```bash
 arcanist environments login owner/repo
@@ -172,28 +165,15 @@ What gets captured is the Playwright storage state for that window: cookies and
 
 The capture needs an interactive terminal: stdin and stderr must be a TTY. Instructions and prompts go to stderr, so `--json --yes --validate-path /dashboard > result.json` works. JSON output is `{environmentId, version, counts: {cookieDomainCount, storageOriginCount}, providerHosts, networkPolicy: {added, rejected, skipped}, validatePath}`, or `{environmentId, deleted}` with `--clear`. `arcanist environments status --json` reports the saved login under `browserState`, including whether a re-login is needed.
 
-### `arcanist setup`
-
-Connect Arcanist and prepare one or more repository environments. The command starts browser authentication when needed, lists only repositories where GitHub reports write access, and queues at most 20 builds.
-
-```bash
-arcanist setup
-arcanist setup acme/web
-arcanist setup acme/web acme/api --json
-arcanist setup acme/web acme/api --workspace
-```
-
-With no repository arguments, the command returns the eligible repositories and `selection_required`. Rerun with the repositories to prepare. `--workspace` prepares them as one multi-repository workspace. Builds continue after the command exits. The command prints an `arcanist environments status owner/repo --wait` command for each build so agents can track progress or leave it running.
-
 ### `arcanist auth login`
 
 ```bash
-arcanist auth login
 printf "arc_..." | arcanist auth login --token-stdin
+arcanist auth login --token arc_...
 arcanist auth login --api-url https://api.tryarcanist.com
 ```
 
-The default flow prints a browser authorization URL and waits for human approval. `--json` writes the action immediately as JSONL on stderr and writes one final result to stdout. `ARCANIST_TOKEN` authenticates later commands through the same config loader as `~/.arcanist/config.json`. `arcanist auth login --token-stdin`, `--token`, or `ARCANIST_TOKEN` persists a token for later use.
+Pass a token via `--token-stdin`, `--token`, or `ARCANIST_TOKEN`; the CLI verifies it against `/api/auth/whoami` and persists it for later use.
 
 ### `arcanist auth whoami`
 
@@ -236,25 +216,6 @@ arcanist codex status --json
 JSON mode returns `{eligible, credential: {isSet, lastValidationStatus?, lastValidationReasonCode?}}`; `eligible` is always
 `true` and remains for compatibility with older clients.
 
-### `arcanist codex logout`
-
-Deactivates the selector and removes the stored Codex subscription auth for your user (write-scoped token).
-
-```bash
-arcanist codex logout
-```
-
-### `arcanist sessions stop <session-id>`
-
-Stops the active run for a session. Idempotent: if no sandbox is active, the server returns `already_stopped`.
-
-```bash
-arcanist sessions stop abc123
-arcanist sessions stop abc123 --json
-```
-
-JSON mode returns `{sessionId, status}`. `status` is the server stop status or, on a 409 stop-block, the block reason; it is an open set. Known values include `stopping`, `stopped`, `already_stopped`, `not_stoppable`, and lifecycle phase names.
-
 ### `arcanist sessions get <session-id>`
 
 ```bash
@@ -291,7 +252,6 @@ arcanist sessions events abc123 --follow --json
 arcanist sessions events abc123 --follow --timeout 60000 --json
 ```
 
-`--after` and `--before` are aliases for `--after-sequence` and `--before-sequence`.
 `--timeout` bounds `--follow`; omit it or pass `0` for unbounded follow. Process exit is a terminal phase, not `session_idle`.
 
 JSON mode without `--follow` returns one JSON object from `/events/history`: `{events: [...], ...}`. Canonical events carry `phase`.
@@ -314,13 +274,6 @@ arcanist sessions transcript abc123 --last 20
 
 `--last <n>` renders only the last `n` stored transcript events after fetching the session export.
 
-### `arcanist sessions usage <session-id>`
-
-```bash
-arcanist sessions usage abc123
-arcanist sessions usage abc123 --json
-```
-
 ### `arcanist sessions artifacts <session-id>`
 
 Lists the artifacts a session produced (screenshots, videos) as `artifactId`, `kind`, `label`, `filename`, `bytes`, `createdAt`.
@@ -355,59 +308,6 @@ arcanist repos list --json
 
 JSON mode returns `{repos, ssoOrgs}`.
 
-### `arcanist repos branches [repo]`
-
-```bash
-arcanist repos branches tryarcanist/arcanist
-arcanist repos branches https://github.com/tryarcanist/arcanist --json
-```
-
-JSON mode returns `{branches}`.
-
-### `arcanist models list`
-
-```bash
-arcanist models list
-arcanist models list --json
-```
-
-JSON mode returns `{models}`.
-
-### `arcanist tokens list`
-
-```bash
-arcanist tokens list
-arcanist tokens list --limit 10 --json
-arcanist tokens list --cursor <cursor> --json
-arcanist tokens list --all --json
-```
-
-`--all` follows cursors until completion and returns `nextCursor: null` in JSON mode.
-
-### `arcanist tokens create`
-
-Creates a CLI token and prints the plaintext token exactly once.
-
-```bash
-arcanist tokens create --scope read
-arcanist tokens create --scope read --expires-in-days 30 --json
-arcanist tokens create --scope read --idempotency-key 1f0e6f1a-...
-```
-
-JSON mode returns `{ok, token, id, scope}`.
-The plaintext token is shown only once.
-Use `--idempotency-key <uuid>` when manually retrying a token create whose first response may have been lost; duplicate keys return `duplicate_request` rather than replaying the raw token.
-Read-scoped tokens cannot create write-scoped tokens; the server enforces that and returns 403.
-
-### `arcanist tokens revoke <id>`
-
-```bash
-arcanist tokens revoke 42
-arcanist tokens revoke 42 --yes --json
-```
-
-Under `--json`, `--yes` is required.
-
 ## Automation recipes
 
 Chain commands with `--json` and `jq`: