@raultov/browser-control-mcp 0.2.0-beta.1 → 0.2.0-beta.2

package/CHANGELOG.md

@@ -10,6 +10,24 @@ from a copy of its code: entries describe the differences from that release.
 
 ## [Unreleased]
 
+## [0.2.0-beta.2] - 2026-10-14
+
+Public **BETA**. Firefox debugger internals only; tool replies are the same
+as in 0.2.0-beta.1.
+
+### Changed
+
+- `bidi-browser-lite` 0.1.5 (`bidi-lite` 0.1.3). Firefox tabs are attached to
+  their debugger with `Debugger::attach_to_context`: Firefox's Remote Agent
+  maps each BiDi context to its RDP tab, replacing the match by position in
+  the tab lists. Tabs on the same URL, several windows and error pages are
+  told apart, and a debugger tool never activates a tab any more (a tab
+  Firefox cannot map is an error, not a guess).
+- Firefox `set_breakpoint` uses bidi-lite's `set_breakpoint_resolved`: the
+  bound column comes from the library (every inline script with the URL is
+  searched). A column-less breakpoint for a script not loaded yet fails with
+  an argument error asking for `column_number`, as before.
+
 ## [0.2.0-beta.1] - 2026-10-13
 
 Public **BETA**. Chrome and Firefox now answer the same replies; several are

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.2.0-beta.1).** This version contains known bugs and differences
+> **Status: BETA (0.2.0-beta.2).** 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
@@ -83,11 +83,11 @@ warnings, CSS warnings, platform messages), in the same shapes as Chrome.
 Each tab's debugger watches them: the session's first tabs are attached when
 the session starts and `open_tab` attaches its tab before loading the URL; a
 tab the page opened is attached by the first `get_console_logs` or
-`get_network_logs` on it. Tabs are matched by their position in BiDi's and
-RDP's tab lists (checked against their URLs), never by activating them; a
-tab that cannot be matched that way (tabs opening or closing at that moment)
-is attached by its first debugger tool, which brings it to the front. Frames
-are captured from the moment a tab is attached.
+`get_network_logs` on it. Firefox itself says which RDP tab shows a BiDi
+tab (its Remote Agent maps the BiDi context to the tab's `browserId`), so
+tabs on the same URL, several windows and error pages are told apart, and a
+tab is never activated or brought to the front to attach it. Frames are
+captured from the moment a tab is attached.
 
 ## 📦 Installation
 
@@ -384,8 +384,10 @@ Both browsers answer the same replies, with 0-based lines everywhere:
 Breakpoint ids are per tab and MCP-level (`bp-1`, `bp-2`...), like tab ids.
 
 Chrome also offers `pause_on_load` (pause on the first statement of the next
-load). Firefox notes: breakpoints by URL only; the column is snapped to the
-nearest breakable position automatically; the debugger needs the RDP port.
+load). Firefox notes: breakpoints by URL only; without `column_number` the
+breakpoint binds to the first breakable column of the line, in whichever of
+the page's scripts with that URL has one (inline `<script>` blocks share the
+page's URL), and needs the script loaded; the debugger needs the RDP port.
 
 ## Migration from chrome-debug-mcp
 
@@ -451,12 +453,9 @@ incompatible:
 - Firefox: after a lost connection a launched Firefox gets a new session on
   the next tool call; an attached Firefox keeps its orphan session, so
   restart that Firefox.
-- Firefox debugger: a tab is matched to its debugger by its position in
-  BiDi's and RDP's tab lists, checked against the tabs' web URLs; tabs
-  showing no web page (`about:blank`, error pages) cannot be checked, so a
-  tab opening or closing elsewhere at that very moment could still bind the
-  debugger to the wrong page. When the lists differ the debugger attaches by
-  activating the tab, as before.
+- Firefox debugger: tabs are mapped to the debugger through Firefox's Remote
+  Agent (verified on Firefox 157 only); a Firefox without it answers the
+  debugger tools with an error instead of guessing a tab.
 - `get_network_logs` with response bodies has no total size limit (each
   Firefox body is capped at 2 MB): use `url_filter` on busy pages.
 - The Docker image is amd64 only.

package/npm-shrinkwrap.json

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

package/package.json

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