@runtypelabs/cli 2.48.2 → 2.53.1

package/README.md

@@ -928,14 +928,14 @@ Manage scheduled flow runs.
 
 Manage API keys. `runtype keys` is an alias.
 
-| Subcommand                  | Description                                      |
-| --------------------------- | ------------------------------------------------ |
-| `api-keys list`             | List your API keys                               |
-| `api-keys get <id>`         | Get API key details                              |
-| `api-keys create -n <name>` | Create a new API key                             |
-| `api-keys delete <id>`      | Delete an API key (`--yes` to skip confirmation) |
-| `api-keys regenerate <id>`  | Regenerate an API key                            |
-| `api-keys analytics`        | Show usage analytics (`--key <id>`)              |
+| Subcommand                              | Description                                             |
+| --------------------------------------- | ------------------------------------------------------- |
+| `api-keys list`                         | List your API keys                                      |
+| `api-keys get <id>`                     | Get API key details                                     |
+| `api-keys create -n <name> -p <scopes>` | Create a new API key (scopes required, comma-separated) |
+| `api-keys delete <id>`                  | Delete an API key (`--yes` to skip confirmation)        |
+| `api-keys regenerate <id>`              | Regenerate an API key                                   |
+| `api-keys analytics`                    | Show usage analytics (`--key <id>`)                     |
 
 ### `runtype products`
 
@@ -1024,6 +1024,40 @@ staging, or local Code Mode host. Local development can override endpoint infere
 Tool calls default to a 930-second client timeout, slightly above Runtype's maximum flow runtime.
 Pass `--timeout <ms>` to use a different positive millisecond deadline.
 
+### `runtype simulations`
+
+Push a sandbox candidate (an agent run as real code in a Runtype sandbox). Simulations run on
+staging, so pass `--api-url https://api.runtype-staging.com` with a staging key.
+
+| Command                                                 | Description                                                       |
+| ------------------------------------------------------- | ----------------------------------------------------------------- |
+| `simulations candidate push <dir or .tgz>`              | Pack (reproducibly) and upload a bundle; prints its `bundle` JSON |
+| `simulations candidate push <path> --create-target <n>` | Also create a `sandbox_candidate` target (`--mcp-target <id>`)    |
+| `simulations candidate push <path> --target <id>`       | Point an existing target at the new bundle, keeping its config    |
+| `simulations candidate push <path> ... --conformance`   | Run the conformance check and print each step                     |
+
+A directory needs `runtype-candidate.json` at its root; it is validated before anything is
+uploaded. `--out <file>` saves the packed archive. See `examples/simulation-candidates/` for
+candidate templates.
+
+### `runtype events`
+
+Watch product events: failed executions, approval requests, failed schedule runs, completed eval
+runs, human takeovers of conversations, and skill proposals.
+
+| Command               | Description                                                      |
+| --------------------- | ---------------------------------------------------------------- |
+| `events types`        | List the event types and the filters each one accepts (`--json`) |
+| `events watch`        | Long-poll events and print one line per event until Ctrl-C       |
+| `events watch --json` | Print NDJSON: exactly one event object per line on stdout        |
+| `events watch --once` | Exit after the first poll that returns events                    |
+
+`events watch` takes `--name <type>` (default: every type), the filters `--agent`, `--flow`,
+`--product`, `--surface`, `--schedule`, `--suite`, `--task`, and `--only-regressions`, and
+`--since <cursor>` (default `now`). Each event carries its `cursor`; pass the last one to `--since`
+to resume without gaps. Events are kept for 7 days. Diagnostics go to stderr, so
+`runtype events watch --json` can feed a monitor that wakes on each line.
+
 ## Configuration
 
 ```bash