browser4-cli 4.14.0-rc.2 → 4.14.0-rc.4

package/README.md

@@ -90,6 +90,8 @@ Choosing the right tool for your task:
 
 Use `snapshot -i --boxes` to see clickable/typeable elements with refs like `e15`, then `click <ref>`, `fill <ref> "<text>"`, `type`/`press`, `select`, `hover`/`drag`/`scroll`, and `wait` to drive the page. All interaction commands accept CSS selectors too. Chain multiple steps efficiently with `batch`.
 
+Content embedded in `<iframe>`s (payment forms, editors, widgets) is reached with the built-in frame switching: `frames` lists the frame tree, `frame "<iframe selector>"` scopes subsequent element commands into that frame (same-origin iframes fully supported), and `frame main` returns to the main document — no manual `contentDocument` eval needed.
+
 Typical interactive flow:
 
 ```bash
@@ -100,6 +102,10 @@ browser4-cli fill e3 "user@example.com"
 browser4-cli fill e4 "secret" --submit
 browser4-cli wait --load networkidle
 browser4-cli snapshot -i
+# iframe-heavy page:
+browser4-cli frame "#pay-frame"
+browser4-cli fill "#card-number" "4111 1111 1111 1111"
+browser4-cli frame main
 ```
 
 ### How to Extract Data
@@ -534,6 +540,30 @@ browser4-cli loop --shell "curl -s https://api.example.com/health" -i 60
 browser4-cli loop --list
 ```
 
+#### Network inspection, HAR recording & request routing
+
+Inspect what the page actually loaded (XHR/fetch calls, status codes, headers,
+response bodies), record a HAR 1.2 archive importable by Chrome DevTools, and
+route (mock/abort) matching requests. See
+[`skills/browser4-cli/references/network.md`](skills/browser4-cli/references/network.md)
+for the full guide.
+
+| Command | Description |
+|---|---|
+| `network requests` | List tracked requests. Supports `--filter`, `--type`, `--method`, `--status` (`200`, `2xx`, `400-499`), `--clear`. |
+| `network request <id>` | Full detail of one request: headers, timing, and the response body (fetched on demand). |
+| `network har start [--content <mode>]` | Start a HAR recording. Content mode: `none`, `text`, or `all` (binary base64). |
+| `network har stop [path]` | Stop recording and print the HAR JSON, or write it to a `.har` file when a path is given. |
+| `network route <pattern> --body <text>\|--abort` | Intercept matching requests (mock response or fail them) via CDP Fetch. Supports `--content-type`, `--resource-type`. |
+| `network unroute [pattern]` | Remove routes; without a pattern, disable interception entirely. |
+
+```bash
+browser4-cli network requests --filter api --status 2xx
+browser4-cli network har start --content text
+browser4-cli network har stop ./capture.har
+browser4-cli network route "**/api/users" --body '{"users":[]}' --content-type application/json
+```
+
 #### Swarm and crawl for scale
 
 The `co` prefix is accepted as an alias for `swarm`.
@@ -754,7 +784,7 @@ The `coding` domain exposes **47 tools** in four groups:
 
 Browser4 includes a lightweight **MockSite** server that serves static HTML pages for testing and demos. Start it from the repository root:
 
-**Windows:** `./bin/test.ps1 mock-site -Dmock.site.port=18080`
+**Windows (pwsh — PowerShell 7+):** `./bin/test.ps1 mock-site -Dmock.site.port=18080`
 **Linux/macOS:** `./bin/test.sh mock-site -Dmock.site.port=18080`
 
 Key demo pages are served at `http://localhost:18080/generated/`. For the full page listing, environment variables, Python fallback, and Maven-based launch, see [MockSite](docs/mocksite.md). For the test taxonomy and tagging system, see [Test Taxonomy](docs/TESTING.md).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "browser4-cli",
-  "version": "4.14.0-rc.2",
+  "version": "4.14.0-rc.4",
   "description": "Browser automation CLI for AI agents",
   "type": "module",
   "files": [