@runalabs/rill-cli 0.1.5 → 0.1.7-beta.0
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.
- package/README.md +19 -0
- package/dist/cli.js +14918 -150
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -6,6 +6,23 @@ Rill starts a local Chromium recorder. Your browser tool drives the returned CDP
|
|
|
6
6
|
|
|
7
7
|
[Getting started](https://userill.dev/docs) · [Website CLI reference](https://userill.dev/docs/cli) · [Agent instructions](https://userill.dev/docs/cli#agents)
|
|
8
8
|
|
|
9
|
+
## Cloud agent beta
|
|
10
|
+
|
|
11
|
+
Invited workspaces can supply a URL and prompt. Cloud runs need Node.js 22+ and a Rill login; Chrome and ffmpeg run on Rill's server.
|
|
12
|
+
|
|
13
|
+
```sh
|
|
14
|
+
rill record https://example.com -p "Open pricing and describe the plans."
|
|
15
|
+
rill record https://example.com/dashboard -p "Describe the dashboard." --account staging
|
|
16
|
+
rill run status <run-id>
|
|
17
|
+
rill run cancel <run-id>
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
The first run opens Rill authorization if needed. Save optional website test accounts in Rill Settings using an account name, exact HTTPS origin, username, password, and optional login URL. Login appears in the private video, with masked password inputs; login diagnostics are omitted. MFA, CAPTCHA, external SSO, and unsupported login forms return a blocker.
|
|
21
|
+
|
|
22
|
+
Cloud recordings are private by default. Closing the terminal disconnects without cancelling. Use `--no-wait` to return after submission, and `--id <same-run-id>` with identical arguments to retry an uncertain submission. Current beta admission is three accepted runs per workspace per UTC day; monthly run credits are not implemented yet.
|
|
23
|
+
|
|
24
|
+
The following local-recording instructions remain available through `record start` and `record stop`.
|
|
25
|
+
|
|
9
26
|
## Install and verify
|
|
10
27
|
|
|
11
28
|
Browser recording runs on macOS and Linux. Install Node.js 22+, Google Chrome or Chromium, and ffmpeg on `PATH`.
|
|
@@ -52,6 +69,8 @@ rill inspect https://userill.dev/s/<share-secret>
|
|
|
52
69
|
|
|
53
70
|
Start returns `recordingId`, `cdpUrl`, `status`, `bodyCaptureEnabled`, and `maxDurationSeconds`. Stop finalizes capture, uploads video and diagnostics, and waits for playback. Confirm `status: "ready"` and a non-null `shareUrl` before returning the evidence link. Local capture finishing does not establish remote readiness.
|
|
54
71
|
|
|
72
|
+
New browser recordings include a visible cursor and click pulses by default. In Rill Settings → Cursor appearance, workspace members can turn them off or choose an accent color. The CLI reads this preference when starting a recording; it is baked into the video and does not change existing recordings. Use an updated CLI and recorder daemon to capture the overlay.
|
|
73
|
+
|
|
55
74
|
### Connect Playwright
|
|
56
75
|
|
|
57
76
|
In a project with `playwright-core` installed, save this as `rill-run.mjs`:
|