@raultov/browser-control-mcp 0.3.0-beta.3 → 0.3.1-beta.3

package/CHANGELOG.md

@@ -10,6 +10,50 @@ from a copy of its code: entries describe the differences from that release.
 
 ## [Unreleased]
 
+## [0.3.1-beta.3] - 2026-10-25
+
+Public **BETA**. Size limits: large pages, results, scripts, logs and
+screenshots no longer flood the agent or drop the browser connection, and
+Chrome reconnects by itself when a reply over 16 MB drops it. Some replies
+change (cut texts end with a `[cut: ...]` or `[Truncated: ...]` note,
+`evaluate_js` may say `truncated: true`, `inspect_dom` positions are
+characters).
+
+### Fixed
+
+- `capture_screenshot` with `full_page` captures at most 16 384 CSS pixels
+  per side, from the top left, and then adds a text note naming the
+  document's size (a 30 000 px page came back whole).
+- Observation buffers keep a bounded copy of each item: a console message
+  keeps 10 000 characters, a WebSocket payload 64 000 (`payload_len` is
+  the whole length), custom event params over 64 000 characters of JSON
+  become `{"truncated": true, "characters": N}`, and `get_network_logs`
+  shows at most 64 000 characters of a request or response body. Each cut
+  text ends with `… [cut: the first N of M characters]`. Chrome no longer
+  fetches a response body whose `Content-Length` is over 2 MB (Firefox
+  keeps none larger). Two 3 MB console messages made a 6 MB reply.
+- `search_scripts` previews a long line (minified code) as the match with
+  100 characters on each side, `…` where it was cut: one hit in a 1.6 MB
+  one-line script returned the whole line.
+- `evaluate_js` returns at most 100 000 characters of `value`: a longer
+  string is cut, and an object or array whose JSON form is longer is
+  measured in the page and only described ("too large to return (N
+  characters of JSON)"), so it never crosses the connection; the reply
+  says `"truncated": true`. A 3-million-element array used to time out on
+  Firefox and a 20 MB object to drop the connection. A string result over
+  16 MB still drops it (the next call reconnects).
+- `inspect_dom` searches and cuts in the page, so a large document no
+  longer crosses the connection (a 20 MB page used to drop it on Chrome).
+  Without `query` it returns at most 100 000 characters, after a
+  `[Truncated: ...]` note naming the total; `before`/`after` are capped at
+  10 000. Positions are characters (they were bytes). On Chrome an
+  exception in the page is an error (it was an empty success).
+- A reply over 16 MB (a huge `evaluate_js` result, a 20 MB page in
+  `inspect_dom`) makes the browser close the DevTools connection. Chrome
+  then answered `CDP Error: Connection lost` to every later call until
+  `restart_browser`; now the next call reconnects by itself (tab ids are
+  re-assigned). The failing call explains what happened on both browsers.
+
 ## [0.3.0-beta.3] - 2026-10-25
 
 Public **BETA**. Result of a tool-by-tool audit on real Chrome and Firefox:

package/README.md

@@ -11,7 +11,7 @@ It is the successor of
 from a copy of its code) and complements Playwright MCP or
 chrome-devtools-mcp with runtime JavaScript debugging on both browsers.
 
-> **Status: BETA (0.3.0-beta.3).** This version contains known bugs and differences
+> **Status: BETA (0.3.1-beta.3).** This version contains known bugs and differences
 > between Chrome and Firefox (see [Limitations and TODO](#limitations-and-todo))
 > and parts that have not been verified (see [Untested](#untested)). Tool
 > replies may change in incompatible ways before 1.0. Please report problems
@@ -49,15 +49,15 @@ see the note.
 | `navigate` | ✓ | ✓ | |
 | `reload` | ✓ | ✓ | |
 | `scroll` | ✓ | ✓ | reports the window positions before and after |
-| `inspect_dom` | ✓ | ✓ | |
-| `capture_screenshot` | ✓ | ✓ | |
+| `inspect_dom` | ✓ | ✓ | at most 100 000 characters without `query` (cut in the page) |
+| `capture_screenshot` | ✓ | ✓ | `full_page` at most 16 384 px per side (a text note says when cut) |
 | `click_element` | ✓ | ✓ | scrolls the element into view; fails without clicking when it is hidden or covered |
 | `fill_input` | ✓ | ✓ | picks `<select>` options; fails without typing on elements that cannot take the text; Chrome inserts the text, Firefox types keys |
 | `handle_dialog` | ✓ | ✓ | accepts or dismisses the open `alert` / `confirm` / `prompt` / `beforeunload` dialog |
-| `evaluate_js` | ✓ | ✓ | |
-| `get_console_logs` | ✓ | ✓ | Firefox: page errors, CSS warnings and platform messages need the debugger port |
-| `get_network_logs` | ✓ | ✓ | Firefox: WebSocket frames need the debugger port |
-| `get_custom_events` | ✓ | partial | Firefox: events of the modules subscribed with `send_bidi_command` |
+| `evaluate_js` | ✓ | ✓ | `value` at most 100 000 characters (`truncated: true`) |
+| `get_console_logs` | ✓ | ✓ | a message keeps at most 10 000 characters; Firefox: page errors, CSS warnings and platform messages need the debugger port |
+| `get_network_logs` | ✓ | ✓ | bodies at most 64 000 characters, none over 2 MB; a WebSocket payload keeps 64 000 (`payload_len` is the whole); Firefox: WebSocket frames need the debugger port |
+| `get_custom_events` | ✓ | partial | params over 64 000 characters of JSON are replaced by `{truncated, characters}`; Firefox: events of the modules subscribed with `send_bidi_command` |
 | `get_performance_metrics` | ✓ | partial | Firefox: `Nodes`, `Frames`, `Resources`, `TransferSize` from the Web Performance APIs (no Performance domain), plus a note |
 | `profile_page_performance` | ✓ | partial | Firefox: FCP, LCP, DCL and Load from the Web Performance APIs; no trace, so `total_blocking_time_ms` and `top_long_tasks` are `null` |
 | `set_breakpoint` | ✓ | partial | Firefox: by URL only (no `script_id` / `script_hash`) |
@@ -65,7 +65,7 @@ see the note.
 | `resume` | ✓ | ✓ | |
 | `step_over` | ✓ | ✓ | |
 | `evaluate_on_call_frame` | ✓ | ✓ | |
-| `search_scripts` | ✓ | ✓ | |
+| `search_scripts` | ✓ | ✓ | a long line's preview is 100 characters on each side of the match |
 | `pause_on_load` | ✓ | ✗ | TODO on Firefox, see [Limitations and TODO](#limitations-and-todo) |
 | `enable_proxy_auth` | ✓ | partial | needs `--proxy-server`; untested on Firefox against a real proxy |
 | `send_cdp_command` | ✓ | ✗ | raw Chrome DevTools Protocol |
@@ -292,6 +292,9 @@ claude mcp add browser-control-mcp -- npx -y @raultov/browser-control-mcp
   by their source, Firefox only as `function`). A thrown exception or a
   rejected promise fails with what was thrown and its 1-based line and
   column, e.g. `ReferenceError: x is not defined (line 1, column 1)`.
+  A `value` over 100 000 characters is not returned whole: a string keeps
+  its first 100 000, an object or array is measured in the page and only
+  described; the reply then carries `"truncated": true`.
 - **Per-tab state.** Console logs, network traffic, breakpoints and custom
   events are kept per tab, in bounded buffers. A tab's console buffer (last
   1000 messages) is cleared when the tab moves to another site (registrable

package/npm-shrinkwrap.json

@@ -19,7 +19,7 @@
       "hasInstallScript": true,
       "license": "MIT",
       "name": "@raultov/browser-control-mcp",
-      "version": "0.3.0-beta.3"
+      "version": "0.3.1-beta.3"
     },
     "node_modules/detect-libc": {
       "engines": {
@@ -48,5 +48,5 @@
     }
   },
   "requires": true,
-  "version": "0.3.0-beta.3"
+  "version": "0.3.1-beta.3"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "artifactDownloadUrls": [
-    "https://github.com/raultov/browser-control-mcp/releases/download/v0.3.0-beta.3"
+    "https://github.com/raultov/browser-control-mcp/releases/download/v0.3.1-beta.3"
   ],
   "author": "raultov <raultov@protonmail.com>",
   "bin": {
@@ -92,7 +92,7 @@
       "zipExt": ".tar.xz"
     }
   },
-  "version": "0.3.0-beta.3",
+  "version": "0.3.1-beta.3",
   "volta": {
     "node": "18.14.1",
     "npm": "9.5.0"