rechrome 1.17.0 → 1.18.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 +32 -0
- package/package.json +1 -1
- package/rech.js +389 -37
- package/rech.ts +389 -37
- package/serve.js +73 -7
- package/serve.ts +73 -7
package/README.md
CHANGED
|
@@ -37,6 +37,38 @@ Now `rechrome` (or `rech`) is available globally.
|
|
|
37
37
|
|
|
38
38
|
## Quick start
|
|
39
39
|
|
|
40
|
+
### 0. One-command setup (recommended)
|
|
41
|
+
|
|
42
|
+
`rech setup` configures the daemon, Chrome extension, and connection URL in one pass:
|
|
43
|
+
|
|
44
|
+
```bash
|
|
45
|
+
rech setup # interactive: pick a profile, follow the prompts
|
|
46
|
+
rech setup --profile you@email.com # non-interactive profile selection
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
What it does per Chrome profile:
|
|
50
|
+
|
|
51
|
+
1. **Daemon** — installs/starts the `serve` daemon (skipped if already healthy).
|
|
52
|
+
2. **Extension** — if the multi-tab extension isn't installed in the chosen profile, it opens an
|
|
53
|
+
install guide **in that exact profile**; load it once via `chrome://extensions → Load unpacked`
|
|
54
|
+
(a one-time manual click — Chrome only allows unpacked extensions through the GUI).
|
|
55
|
+
3. **Token** — once the extension is present, the auth token is **read automatically** from the
|
|
56
|
+
profile's `localStorage` (no copy-paste). For headless/agent runs you can also pass it
|
|
57
|
+
explicitly:
|
|
58
|
+
|
|
59
|
+
```bash
|
|
60
|
+
rech setup --profile 18 --token <PLAYWRIGHT_MCP_EXTENSION_TOKEN> # or RECH_TOKEN=… rech setup …
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
`setup` is agent-friendly: it never blocks on a TTY, opens the guide in the right profile, and
|
|
64
|
+
auto-reads the token, so a non-interactive run completes end-to-end once the extension is loaded.
|
|
65
|
+
|
|
66
|
+
> **Managed QA profiles (experimental):** `rech provision-profile <name> --experimental` spins up a
|
|
67
|
+
> fully isolated profile on **Chrome for Testing** (run `npx playwright install chromium` first) with
|
|
68
|
+
> the extension auto-loaded and the token auto-seeded — zero GUI, zero TTY. It is *not* your real
|
|
69
|
+
> Chrome (branded Google Chrome 149+ rejects `--load-extension`), so it has no logins/cookies; use it
|
|
70
|
+
> for clean QA fixtures, and `rech setup` for your real, logged-in Chrome.
|
|
71
|
+
|
|
40
72
|
### 1. Start the server
|
|
41
73
|
|
|
42
74
|
On the machine with a browser:
|