@pyrokine/mcp-chrome 3.0.0 → 3.0.1

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.
Files changed (65) hide show
  1. package/README.md +119 -38
  2. package/README_zh.md +165 -110
  3. package/dist/core/browser-driver.d.ts +5 -4
  4. package/dist/core/browser-driver.d.ts.map +1 -1
  5. package/dist/core/browser-driver.js.map +1 -1
  6. package/dist/core/errors.d.ts +6 -4
  7. package/dist/core/errors.d.ts.map +1 -1
  8. package/dist/core/errors.js +14 -8
  9. package/dist/core/errors.js.map +1 -1
  10. package/dist/core/locator.d.ts +7 -0
  11. package/dist/core/locator.d.ts.map +1 -1
  12. package/dist/core/locator.js +48 -25
  13. package/dist/core/locator.js.map +1 -1
  14. package/dist/core/session.d.ts +6 -4
  15. package/dist/core/session.d.ts.map +1 -1
  16. package/dist/core/session.js +58 -23
  17. package/dist/core/session.js.map +1 -1
  18. package/dist/core/unified-session.d.ts +11 -8
  19. package/dist/core/unified-session.d.ts.map +1 -1
  20. package/dist/core/unified-session.js +71 -27
  21. package/dist/core/unified-session.js.map +1 -1
  22. package/dist/extension/bridge.d.ts +3 -3
  23. package/dist/extension/bridge.d.ts.map +1 -1
  24. package/dist/extension/bridge.js +50 -20
  25. package/dist/extension/bridge.js.map +1 -1
  26. package/dist/extension/http-server.d.ts.map +1 -1
  27. package/dist/extension/http-server.js +9 -0
  28. package/dist/extension/http-server.js.map +1 -1
  29. package/dist/tools/browse.d.ts.map +1 -1
  30. package/dist/tools/browse.js +10 -4
  31. package/dist/tools/browse.js.map +1 -1
  32. package/dist/tools/challenge.d.ts.map +1 -1
  33. package/dist/tools/challenge.js +12 -15
  34. package/dist/tools/challenge.js.map +1 -1
  35. package/dist/tools/evaluate.d.ts.map +1 -1
  36. package/dist/tools/evaluate.js +10 -0
  37. package/dist/tools/evaluate.js.map +1 -1
  38. package/dist/tools/extract.d.ts.map +1 -1
  39. package/dist/tools/extract.js +30 -22
  40. package/dist/tools/extract.js.map +1 -1
  41. package/dist/tools/input.d.ts.map +1 -1
  42. package/dist/tools/input.js +83 -57
  43. package/dist/tools/input.js.map +1 -1
  44. package/dist/tools/manage.d.ts.map +1 -1
  45. package/dist/tools/manage.js +16 -30
  46. package/dist/tools/manage.js.map +1 -1
  47. package/dist/tools/post-condition.d.ts.map +1 -1
  48. package/dist/tools/post-condition.js +23 -9
  49. package/dist/tools/post-condition.js.map +1 -1
  50. package/dist/tools/target-diagnostics.d.ts +9 -1
  51. package/dist/tools/target-diagnostics.d.ts.map +1 -1
  52. package/dist/tools/target-diagnostics.js +60 -17
  53. package/dist/tools/target-diagnostics.js.map +1 -1
  54. package/dist/tools/wait.d.ts.map +1 -1
  55. package/dist/tools/wait.js +19 -7
  56. package/dist/tools/wait.js.map +1 -1
  57. package/extension/dist/assets/{content.ts-loader-CnJuCGhl.js → content.ts-loader-DUWbDHRS.js} +1 -1
  58. package/extension/dist/assets/{content.ts-C4imZ6A9.js → content.ts-qe6IB5DK.js} +1 -1
  59. package/extension/dist/assets/{index.ts-GeHNZBml.js → index.ts-D7_LCUoV.js} +559 -212
  60. package/extension/dist/assets/{page-scripts-CMIY1zhd.js → page-scripts-D508WLkW.js} +50 -51
  61. package/extension/dist/assets/{popup.html-CgtWL6Py.js → popup.html-B-eVq48O.js} +6 -4
  62. package/extension/dist/manifest.json +4 -4
  63. package/extension/dist/service-worker-loader.js +1 -1
  64. package/extension/dist/src/popup/popup.html +1 -1
  65. package/package.json +12 -6
package/README.md CHANGED
@@ -38,6 +38,27 @@ existing browser, **CDP mode** (fallback) launches a dedicated instance.
38
38
  Local zero-config auto-connect is unchanged. Reloading the Extension or restarting the MCP client does not require a
39
39
  manual Connect click.
40
40
 
41
+ ## Request scope and failure handling
42
+
43
+ An input sequence keeps its selected backend and page until the sequence and target restoration finish. Concurrent
44
+ `browse(action="connect")` waits for that scope. A CDP request with `frame` returns a capability error before resolving
45
+ or operating on an Extension page. Extension frame resolution checks the selected document and probes the native iframe
46
+ owner, so reordering same-URL frames cannot redirect execution by a stale DOM index.
47
+
48
+ Explicit `wait="networkidle"` enables Network observation before navigation and waits for requests to finish followed by
49
+ 500 ms of quiet. Missing or interrupted observation returns an error; the default `load` path does not attach a debugger
50
+ for network-idle tracking. CDP network logs retain the HTTP status when a response body fails and record one terminal
51
+ entry per request. Temporary CDP page selection preserves separate log buffers for each target.
52
+
53
+ Input `timeout` includes page selection, preparation and key RPCs. An acknowledgement that arrives after the deadline
54
+ cannot produce success; uncertain execution is reported as `actionStatus="unknown"` with `retryable=false`. Read the
55
+ current page state before deciding the next action.
56
+
57
+ Group operations serialize with page release and recheck membership and managed authority while holding the affected
58
+ page locks. For page creation, use `active`; `activate` is accepted only by `movePage`. Popup settings report failed
59
+ storage writes, and delayed stored values cannot override a newer setting. Default local auto-connect remains enabled
60
+ without a manual pairing or connection step.
61
+
41
62
  ## Compatible Clients
42
63
 
43
64
  | Client | Status |
@@ -288,6 +309,10 @@ page. `releasePage` revokes full managed access without closing the tab or chang
288
309
  log state and removes debugging and console capture resources. If Chrome prevents resource cleanup, the response
289
310
  includes `warnings` while managed access is still revoked.
290
311
 
312
+ Managed access survives a Service Worker restart. Reloading the Extension also restores access to surviving managed
313
+ tabs whose original document identity still matches, without refreshing or adopting them again. Tabs with unavailable
314
+ document identity require explicit `adoptPage` after an Extension reload; ordinary navigation keeps managed access,
315
+ and `releasePage` remains revoked after a restart or reload. A reused tab ID does not authorize a different document.
291
316
  A managed tab can keep using this Extension's existing debugger session after a Service Worker restart. Sessions owned
292
317
  by other debuggers still return `DEBUGGER_BLOCKED`.
293
318
 
@@ -308,9 +333,11 @@ page is closed; it never authorizes content access.
308
333
  ### Access challenges
309
334
 
310
335
  After `open`, `back`, `forward`, `refresh`, `input`, and `evaluate`, MCP Chrome waits for a Cloudflare JS Challenge or
311
- Turnstile checkbox. When Extension mode is active, navigation starts without debugger logging and reads the live tab
312
- title passively for eight seconds. If the interstitial persists, MCP Chrome checks for a visible Turnstile control and
313
- clicks it only when it finds one. Extension inspect uses an isolated world and detaches the debugger first. Same-page
336
+ Turnstile checkbox. When Extension mode is active, navigation starts without debugger logging. While a Challenge title
337
+ persists, MCP Chrome reads the live tab title passively for the first eight seconds. If the interstitial persists, it checks for a visible Turnstile control and
338
+ clicks it only when it finds one. Extension inspect uses an isolated world. Challenge titles detach the debugger before
339
+ inspection; ordinary-page checks retain an existing connection unless a visible verification control or unresolved
340
+ challenge content is found. Same-page
314
341
  fixture buttons use the existing page click. If a Cloudflare Turnstile iframe is present, inspect CSS coordinates are
315
342
  converted to screen coordinates and the OS mouse moves along a path, hovers, then presses and releases: `xdotool` on
316
343
  Linux uses the focused Chrome client-window geometry and `xprop` GTK frame extents only when that window title matches
@@ -328,12 +355,15 @@ is clicked at most once; if Cloudflare then shows a visible `Verify you are huma
328
355
  button is inspected as `verify` and clicked at most once in the same wait. Use the default `diagnostics=false` for
329
356
  challenge-protected pages because diagnostics starts debugger console and network collection.
330
357
 
331
- Detection covers titles such as `Just a moment...` and `请稍候…`, challenge DOM or body-text markers, and
332
- `Verify you are human` / `请验证您是真人` controls, including visible `button` elements with that exact text. Same-page
333
- buttons use page input when no Cloudflare iframe is present. CDP reads live titles with `Target.getTargetInfo`. A
334
- leftover Cloudflare iframe on a recovered page is not pending. Cached titles do not decide the result. MCP Chrome does
335
- not call a CAPTCHA solver, retry navigation, or export `cf_clearance` values. A CDP timeout does not prove that the site
336
- fails in a user Chrome session; check the returned `mode` before diagnosing the site.
358
+ Detection covers titles such as `Just a moment...` and `请稍候…`, visible challenge DOM or body-text markers, and
359
+ `Verify you are human` / `请验证您是真人` controls, including visible `button` elements with that exact text. A normal
360
+ title still requires a bounded check of visible content: visible `正在进行安全验证` blocks the action, while hidden
361
+ markers do not. Pages without challenge evidence continue without a fixed eight-second wait. Same-page buttons use
362
+ page input when no Cloudflare iframe is present. CDP reads live titles with `Target.getTargetInfo`. A leftover
363
+ Cloudflare iframe or an old pending header alone does not keep a recovered page pending or trigger scrolling or a
364
+ click. Cached titles do not decide the result. MCP Chrome does not call a CAPTCHA solver, retry navigation, or export
365
+ `cf_clearance` values. A CDP timeout does not prove that the site fails in a user Chrome session; check the returned
366
+ `mode` before diagnosing the site.
337
367
 
338
368
  A resolved challenge returns `challengeResolved=true`, `challengeKind`, `waitedMs`, `clickedTurnstile`, and
339
369
  `clearanceCookiePresent` (name presence only). If the visible page text says verification succeeded and Cloudflare is
@@ -371,7 +401,10 @@ Special-case parameters:
371
401
  - `keydown` accepts `commands` (e.g. `["selectAll"]`, `["copy"]`, `["paste"]`, `["cut"]`, `["undo"]`, `["redo"]`) to
372
402
  trigger native browser editing commands. A successful response means the browser accepted the command dispatch; use
373
403
  `postCondition` or `extract` to verify the page result. `commands` is precise-mode only; stealth mode throws because
374
- the CDP commands API has no JS-event equivalent.
404
+ the CDP commands API has no JS-event equivalent. An element or coordinate `target` is focused without mouse events
405
+ before command dispatch. Coordinate focus does not toggle checkboxes, follow links, or invoke click listeners. A
406
+ missing or unfocusable target returns an error before commands are sent. Extension `frame` coordinates are local to
407
+ that frame.
375
408
  - `keydown` on a key already held emits `rawKeyDown` with `autoRepeat: true` (Puppeteer-compatible long-press).
376
409
 
377
410
  `events` must contain at least one event. Parameters: `humanize` enables Bézier curve movement and random delays.
@@ -384,6 +417,11 @@ check. `targetId` (or legacy `tabId`) selects a page in either backend; `frame`
384
417
  index) in Extension mode. When either scope is provided, the action, diagnostics, and post-condition use the backend
385
418
  selected for that target scope.
386
419
 
420
+ If the frame, execution context, or debugger becomes unavailable during verification, the check returns
421
+ `verificationStatus="unavailable"`. A script that throws or rejects, even with the same error text, returns `error`.
422
+ An already completed action keeps `actionStatus="completed"` and `failureStage="verification"`; verification does not
423
+ replay the action.
424
+
387
425
  For keyboard `type`, `timeout` includes Challenge waiting, focus preparation, character input, and `delay`/`humanize`
388
426
  delays. Extension precise/stealth and CDP use the remaining budget. An explicit budget such as `timeout=45000` allows
389
427
  valid input to take longer than the default 30000 ms. When the budget expires, subsequent characters and events stop.
@@ -399,6 +437,10 @@ Command focus, text selection, and replacement share the remaining event budget.
399
437
  release is still attempted without hiding an earlier action error. Stepped CDP touch movement also stops at the
400
438
  deadline.
401
439
 
440
+ Stealth left clicks emit `click`, middle clicks emit `auxclick`, and right clicks emit `contextmenu`. Each press/release
441
+ pair carries its click `detail`; only left multiple clicks emit `dblclick` at `detail=2`. Separate stealth `mouseup`
442
+ events follow the same button mapping.
443
+
402
444
  In stealth mode, `delay` separates characters; the first character has no initial wait. Background page timer throttling
403
445
  can lengthen subsequent intervals, but the same deadline still stops further input.
404
446
 
@@ -426,6 +468,13 @@ omitted from failure diagnostics, and input `find` or replacement `text` values
426
468
  matching element; both are zero-based and may be used together. Locator targets for `select` and `replace` work in CDP
427
469
  mode without Extension ref IDs.
428
470
 
471
+ In both backends, target lookup failures from `input`, `extract`, and `wait` report the failed locator, zero-based `nth`,
472
+ URL, tab/frame scope, managed state, last locator state, and at most 10 candidate summaries within the request budget.
473
+ `matchCount` is the observed total, not the candidate limit; an out-of-range `nth` does not turn 15 matches into zero.
474
+ Unknown counts or managed state are `null`, and unavailable diagnostics include `diagnosticError`. CDP retains
475
+ `ELEMENT_NOT_FOUND` for lookup failures and `TIMEOUT` for element waits, together with existing URL and log fields.
476
+ Diagnostics read the failed target before its scope is restored and never replay input.
477
+
429
478
  ### extract - Content Extraction
430
479
 
431
480
  | Type | Description |
@@ -470,9 +519,12 @@ describes Extension page management; CDP returns false without restricting norma
470
519
  `computed:font-size`). Use `computed:*` to return all computed style properties as JSON (returns 300+ properties — use
471
520
  `output` to save to file).
472
521
 
473
- **`state`-specific**: `depth` controls DOM traversal depth (default 15). Reduce to limit response size on large pages.
474
- `mode` selects the underlying source — `accessibility` (default, derived from the a11y tree) or `domsnapshot` (raw CDP
475
- `DOMSnapshot.captureSnapshot`, CDP-only; returns a flat node array with computed styles for advanced post-processing).
522
+ **`state`-specific**: `depth` controls accessibility-tree traversal depth (default 15). Reduce it to limit response size
523
+ on large pages. `mode` selects `accessibility` (default, derived from the a11y tree) or `domsnapshot` (raw
524
+ `DOMSnapshot.captureSnapshot`, available through CDP or a managed Extension page). DOMSnapshot captures the whole page
525
+ and rejects `target`, `frame`, and `depth` instead of ignoring those limits. Ordinary read grants do not grant debugger
526
+ access. Unavailable sibling iframe probes are listed in metadata as `unavailableFrames` and per-frame
527
+ `unavailableReason`; a uniquely verified selected iframe remains usable.
476
528
 
477
529
  ### wait - Wait for Conditions
478
530
 
@@ -525,9 +577,11 @@ action. `postCondition` is optional; when it is not provided, `success=true` onl
525
577
  returned. When it is provided and does not match before timeout, the tool returns `POST_CONDITION_FAILED` with the last
526
578
  observed checks. Precise iframe evaluation does not replay a script after a stale execution context by default. Set
527
579
  `staleContextRetry="readOnly"` only when the script has no side effects; the Extension may then resolve a new context
528
- and replay it once within the remaining timeout budget. A stale-context error after `Runtime.evaluate` reports
529
- `actionExecuted=true` and `actionStatus="unknown"`, because earlier side effects may already have happened even though
530
- the final result is unavailable.
580
+ and replay it once within the remaining timeout budget. If Chrome still reports the removed document while resolving
581
+ that retry, the Extension waits for the current document within the same budget; this does not add script executions.
582
+ Permission failures stop immediately. A stale-context error after `Runtime.evaluate` reports `actionExecuted=true` and
583
+ `actionStatus="unknown"`, because earlier side effects may already have happened even though the final result is
584
+ unavailable.
531
585
 
532
586
  For object results in the main frame with Extension precise mode, an explicit `output` uses a 16 Mi (16777216) character
533
587
  budget. Without `output`, the 1000000-character budget still applies, including automatic saving. Both paths retain the
@@ -551,7 +605,7 @@ result limit reports the current limit and the completed script's output failure
551
605
  | `reorderPage` | Reorder a controlled tab inside its window |
552
606
  | `pinPage` | Pin a controlled tab |
553
607
  | `unpinPage` | Unpin a controlled tab |
554
- | `activatePage` | Activate a controlled tab and focus its window |
608
+ | `activatePage` | Activate an explicit page; Extension requires a controlled tab |
555
609
  | `focusWindow` | Focus an explicit window |
556
610
  | `resizeWindow` | Resize or change state for an explicit window |
557
611
  | `newWindow` | Create a new controlled window |
@@ -569,17 +623,27 @@ result limit reports the current limit and the completed script's output failure
569
623
  | `stealth` | Inject anti-detection scripts |
570
624
  | `cdp` | Send raw CDP command (advanced, e.g. `Runtime.evaluate`) |
571
625
 
572
- Native tab/window/group configuration is Extension-mode only. Mutations identify their existing targets with `targetId`,
573
- `targetIds`, `windowId`, or `groupId` and return `affected.before/after`. Group results also include
574
- `tabsBefore/tabsAfter`; `ungroupPages` removes an empty group through Chrome without revoking the tabs' managed state.
575
- Group title/color/collapse updates and group moves require all group members to be managed. Window updates, resizing,
576
- and focusing require all window tabs to be managed; a cached MCP window ID does not override that check. `clearCache` is
577
- unavailable in Extension mode and returns `UNSUPPORTED_MODE` without clearing anything. Use scoped
578
- `cookies(action="clear")` for cookies or CDP mode for storage and cache. `focusWindow` only returns success after the
579
- target window is observed as focused; otherwise it returns `WINDOW_FOCUS_NOT_OBSERVED`. `closeWindow` refuses mixed
580
- windows with unmanaged tabs and returns `WINDOW_HAS_UNMANAGED_TABS`. Persistent `adoptPage` and `releasePage` target
581
- changes are serialized with scoped tab operations, so a concurrent multi-event input remains on its requested tab and
582
- the persistent target is applied afterward.
626
+ Native tab/window/group configuration uses Extension mode; `activatePage` also supports CDP. Mutations identify their
627
+ existing targets with `targetId`, `targetIds`, `windowId`, or `groupId` and return `affected.before/after`. Group
628
+ results also include `tabsBefore/tabsAfter`; `ungroupPages` removes an empty group through Chrome without revoking the
629
+ tabs' managed state. Window display changes and group title/color/collapse updates use the explicit `windowId` or
630
+ `groupId`, including containers with unmanaged members. They do not grant page permissions. Group moves and window
631
+ closure still require every affected member to be managed. Grouping or ungrouping selected pages checks those pages;
632
+ unrelated sibling changes do not invalidate a valid selection. Default page creation reuses a valid cached MCP window
633
+ even when it contains unmanaged tabs. `clearCache` is unavailable in Extension mode and returns `UNSUPPORTED_MODE`
634
+ without clearing anything. Use scoped `cookies(action="clear")` for cookies or CDP mode for storage and cache.
635
+ `focusWindow` only returns success after the target window is observed as focused; otherwise it returns
636
+ `WINDOW_FOCUS_NOT_OBSERVED`. `closeWindow` refuses mixed windows with unmanaged tabs and returns
637
+ `WINDOW_HAS_UNMANAGED_TABS`. Persistent `adoptPage` and `releasePage` target changes are serialized with scoped tab
638
+ operations, so a concurrent multi-event input remains on its requested tab and the persistent target is applied
639
+ afterward.
640
+
641
+ CDP `activatePage` retains the default operation target and reports the fields available from that backend, without
642
+ inventing an `active` value or system-window focus. In Extension mode, `viewport`, `userAgent`, `emulate`, raw `cdp`,
643
+ and precise `evaluate` support controlled `about:blank` pages. Chrome-internal and Extension pages retain their access
644
+ restrictions. Querying `manage(action="emulate")` without `device` returns the local device catalogue without a live
645
+ page; page conditions are rejected for this query. Setting a device continues to validate the selected page and
646
+ conditions.
583
647
 
584
648
  | Action | Native parameters | Behavior |
585
649
  | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
@@ -607,6 +671,11 @@ omitted; full details use `favIconInline=true` to indicate one exists. Groups re
607
671
  state, window, first-member index and member IDs. Color belongs to a group, not a tab. Readonly properties are returned
608
672
  when Chrome supplies them, not accepted as configuration writes. Listing does not read page content, navigate or focus.
609
673
 
674
+ Older Extensions that return group summaries without member arrays use the same response's window/tab membership to
675
+ populate group members and first-member index. Summary/full details and filters remain available without another RPC.
676
+ If group information is absent entirely, `groups` is omitted with a warning that it is unavailable. A supplied
677
+ `groups: []` means no groups. Malformed group data, including only one member array, returns an error.
678
+
610
679
  Moving tabs/groups accepts `index=-1`; page creation requires a nonnegative index. Opener and explicit group/window
611
680
  options must identify the same window. Pinned tabs cannot be created inside a group. Window state/bounds conflicts and
612
681
  action-inappropriate fields are rejected before mutation. CDP rejects unsupported Chrome UI options rather than ignoring
@@ -966,20 +1035,29 @@ MIT License - see [LICENSE](LICENSE) for details.
966
1035
  Input and evaluate responses append `actionExecuted`, `actionStatus`, `verificationStatus`, `failureStage`, and
967
1036
  `retryable`. Verification uses `matched`, `not_matched`, `unavailable`, or `error`; debugger timeouts report the action
968
1037
  as `unknown` when completion cannot be proven. Page-thrown exceptions report `actionExecuted=true` with
969
- `actionStatus="failed"`; result materialization or serialization errors report `actionStatus="completed"` and
970
- `failureStage="output"`. Diagnostics are best-effort and return `diagnosticsStatus` without replacing the main action
1038
+ `actionStatus="failed"`. Once native execution returns a result, local materialization or serialization failures report
1039
+ `actionStatus="completed"` and `failureStage="output"`. Diagnostics are best-effort and return `diagnosticsStatus` without replacing the main action
971
1040
  result. On a page precondition mismatch, input and evaluate report `actionExecuted=false` and
972
1041
  `actionStatus="not_started"`. Browse and wait errors also retain any diagnostics collected before the action failed.
973
1042
  Target diagnostics query the current tab state instead of relying on cached attach metadata.
974
1043
 
975
- Native script termination and `Internal error` responses from CDP `Runtime` script commands preserve the original error
976
- code. evaluate and `manage cdp` return `actionExecuted=true`, `actionStatus="unknown"`, and `retryable=false` without
977
- replaying the command. evaluate also returns `retryable=false` when an in-flight RPC timeout or stale execution context
978
- leaves the result unknown; timeouts before execution starts remain retryable. Page-thrown exceptions with the same text
979
- remain action failures.
1044
+ Native script termination, `Internal error`, `Object couldn't be returned by value`, and `Object reference chain is too long`
1045
+ responses from CDP `Runtime` script commands preserve the original error code. evaluate and `manage cdp` return `actionExecuted=true`,
1046
+ `actionStatus="unknown"`, and `retryable=false` without replaying the command. evaluate also returns `retryable=false`
1047
+ when an in-flight RPC timeout or stale execution context leaves the result unknown; timeouts before execution starts
1048
+ remain retryable. Page-thrown exceptions with the same text remain non-retryable action failures.
1049
+
1050
+ Recognized Extension CDP rejections return `CDP_ERROR` with the method, target, native message and available protocol
1051
+ code. The context distinguishes a disabled Debugger domain, stale script ID, browser-level command restriction, missing
1052
+ method, command permission refusal (`Not allowed`), and native result serialization failure. A resource or method lookup failure does not imply that the entire
1053
+ domain is unsupported. These remain failed calls with warning diagnostics; unknown errors retain error-level reporting.
1054
+ A closed tab found during a native snapshot or permission check remains a target failure, separate from page-thrown
1055
+ exceptions with matching text.
980
1056
 
981
- Extension accessibility state does not read password values to generate element names. Labels, placeholders, titles, and
982
- ordinary input values remain available. Explicit script, HTML, and attribute reads retain their existing behavior.
1057
+ Extension accessibility state never reads `input[type=hidden]` or `input[type=password]` value getters for element names
1058
+ or state text. This applies to the default `all` filter, target subtrees, and file output. Hidden controls may still
1059
+ appear with `visible=false`; labels, placeholders, titles, and ordinary input values remain available. Explicit script,
1060
+ HTML, and attribute reads retain their existing behavior.
983
1061
 
984
1062
  `replace` uses text selection only for `textarea` and input types `text`, `search`, `tel`, `url`, and `password`. Other
985
1063
  input types use a native full-value update and return the requested and actual browser-normalized values. A standalone
@@ -996,6 +1074,9 @@ replay stale scripts. `readOnly` permits one replay after the Extension verifies
996
1074
  execution context. Responses include the policy, `retryAttempted`, bounded `retryReason`, and the final `frameContext`
997
1075
  with the Extension frame, parent frame, URL, CDP frame, and execution context IDs. Same-URL frames are rejected only
998
1076
  when the selected DOM iframe cannot identify one target. Existing iframe targets remain usable after an Extension reload
999
- without refreshing or navigating the page. Port scanning aggregates ordinary pre-open failures at debug level;
1077
+ without refreshing or navigating the page. Invalidated probe contexts produce a warning and stop listening instead of
1078
+ throwing an uncaught messaging error. Discovery reports the initial port set and subsequent changes, including transitions
1079
+ to no servers; unchanged scans and automatic reconnects do not repeat that summary. Each scan still checks the entire
1080
+ port range. Explicit disconnect starts a new reporting cycle. Ordinary pre-open failures remain debug-level;
1000
1081
  authentication and protocol rejections from identified MCP servers produce one bounded warning when the rejection
1001
1082
  summary changes.