Merge branch 'main' into fix/reject-json-array-tool-params

Author: wolfib

.github/workflows/pre-release.yml

@@ -52,6 +52,7 @@ jobs:
           NODE_ENV: 'production'
 
       - name: Verify server.json
+        if: runner.os == 'Linux'
         shell: bash
         run: npm run verify-server-json-version
 

.gitmodules

@@ -3,3 +3,4 @@
 	url = https://github.com/ChromeDevTools/devtools-frontend.git
 	branch = main
 	shallow = true
+	fetchRecurseSubmodules = false

docs/configuration.md

@@ -168,11 +168,11 @@ The Chrome DevTools MCP server supports the following configuration option:
   - **Type:** number
 
 - **`--blockedUrlPattern`/ `--blocked-url-pattern`**
-  Restricts browser's network access by blocking specified URL patterns (uses https://urlpattern.spec.whatwg.org/). Silently detaches from targets with blocked URLs upon connection, and blocks runtime requests (including navigations and subresources). Accepts an array of patterns.
+  Restricts browser's network access by blocking specified URL patterns (uses https://urlpattern.spec.whatwg.org/). Silently detaches from targets with blocked URLs upon connection, and blocks runtime requests (including navigations and subresources). Accepts an array of patterns. A pattern that uses a regexp group in any component (for example `(127\.\d+\.\d+\.\d+)` in the hostname) is rejected, because it is not enforced on redirects or subresources; use an exact value or a `*`/`:name` wildcard instead.
   - **Type:** array
 
 - **`--allowedUrlPattern`/ `--allowed-url-pattern`**
-  Restricts browser's network access by allowing only specified URL patterns (uses https://urlpattern.spec.whatwg.org/). Requires Chrome 149+. Silently detaches from targets with unallowed URLs upon connection, and blocks runtime requests (including navigations and subresources). Accepts an array of patterns.
+  Restricts browser's network access by allowing only specified URL patterns (uses https://urlpattern.spec.whatwg.org/). Requires Chrome 149+. Silently detaches from targets with unallowed URLs upon connection, and blocks runtime requests (including navigations and subresources). Accepts an array of patterns. A pattern that uses a regexp group in any component (for example `(127\.\d+\.\d+\.\d+)` in the hostname) is rejected, because it is not enforced on redirects or subresources; use an exact value or a `*`/`:name` wildcard instead.
   - **Type:** array
 
 - **`--performanceCrux`/ `--performance-crux`**

docs/tool-reference.md

@@ -404,8 +404,10 @@
 
 ### `get_css_styles`
 
-**Description:** Retrieve matched CSS rules, inline styles, inherited styles, and cascade information for an element identified by its UID.
-Use this tool to debug why specific CSS properties are applied, overridden, or conflicting. Results are paginated and return 10 rules per page by default; use pageIdx to page through the remaining rules. Requires a UID from [`take_snapshot`](#take_snapshot).
+**Description:** Retrieve matched CSS rules, inline styles (element.style), inherited styles, custom properties, and cascade wrappers (@layer, @media, @container, @scope) for an element identified by its UID.
+Rules are ordered from highest to lowest cascade precedence and include source line numbers (e.g. index:196). Active (winning) declarations have no prefix tag, while (losing) overridden declarations are prefixed with [overloaded].
+Treat the output as authoritative and complete.
+Results are paginated (10 rules per page by default); use pageIdx to page through the remaining rules. Requires a UID from [`take_snapshot`](#take_snapshot).
 
 **Parameters:**
 

package-lock.json

@@ -11,6 +11,7 @@
   "scripts": {
     "cli:generate": "node scripts/generate-cli.ts",
     "clean": "node -e \"require('fs').rmSync('build', {recursive: true, force: true})\"",
+    "clean:submodules": "node scripts/clean-submodules.ts",
     "bundle": "npm run clean && npm run build && rollup -c rollup.config.js && node -e \"require('fs').rmSync('build/node_modules', {recursive: true, force: true})\" && node scripts/append-lighthouse-notices.ts",
     "build": "tsc && node scripts/post-build.ts",
     "typecheck": "tsc --noEmit",
@@ -76,10 +77,10 @@
     "eslint-import-resolver-typescript": "^4.4.4",
     "eslint-plugin-import": "^2.32.0",
     "globals": "^17.0.0",
-    "lighthouse": "13.4.1",
+    "lighthouse": "13.5.0",
     "prettier": "^3.6.2",
-    "puppeteer": "25.11.0",
-    "rollup": "4.63.3",
+    "puppeteer": "25.12.0",
+    "rollup": "4.63.4",
     "rollup-plugin-cleanup": "^3.2.1",
     "rollup-plugin-license": "^3.6.0",
     "semver": "^7.7.4",

package.json

@@ -0,0 +1,32 @@
+/**
+ * @license
+ * Copyright 2026 Google LLC
+ * SPDX-License-Identifier: Apache-2.0
+ */
+
+import {rmSync, existsSync} from 'node:fs';
+import {resolve} from 'node:path';
+
+const projectRoot = process.cwd();
+
+console.log('Cleaning submodules...');
+
+const directoriesToRemove = [
+  resolve(projectRoot, 'third_party', 'devtools-frontend'),
+  resolve(projectRoot, '.git', 'modules', 'devtools-frontend'),
+];
+
+for (const dir of directoriesToRemove) {
+  try {
+    if (existsSync(dir)) {
+      rmSync(dir, {recursive: true, force: true});
+      console.log(`Removed ${dir}`);
+    }
+  } catch (error) {
+    console.error(`Failed to remove ${dir}:`, error);
+  }
+}
+
+console.log(
+  'Submodules cleaned. You can now run `npm run prepare` to re-initialize them.',
+);

scripts/clean-submodules.ts

@@ -5,7 +5,7 @@
  */
 
 import {execSync} from 'node:child_process';
-import {existsSync, readFileSync, writeFileSync} from 'node:fs';
+import {existsSync, readFileSync, writeFileSync, rmSync} from 'node:fs';
 import {resolve} from 'node:path';
 
 const projectRoot = process.cwd();
@@ -51,29 +51,60 @@ function ensureSubmodule(): void {
     return;
   }
 
-  console.log('Initializing devtools-frontend submodule...');
+  console.log(
+    'Initializing devtools-frontend submodule with sparse checkout...',
+  );
   try {
-    execSync('git submodule update --init --depth 1', {
+    const gitModuleDir = resolve(
+      projectRoot,
+      '.git',
+      'modules',
+      'devtools-frontend',
+    );
+    // If the submodule was previously initialized (e.g. as a full checkout),
+    // the existing directories will cause `git clone` or `absorbgitdirs` to fail.
+    // We clean them up here to ensure the sparse checkout initialization succeeds.
+    if (existsSync(devtoolsFrontendDir)) {
+      rmSync(devtoolsFrontendDir, {recursive: true, force: true});
+    }
+    if (existsSync(gitModuleDir)) {
+      rmSync(gitModuleDir, {recursive: true, force: true});
+    }
+
+    // 1. Clone only the tree structure of the default branch (no blobs)
+    execSync(
+      'git clone --no-checkout --depth 1 --filter=blob:none https://github.com/ChromeDevTools/devtools-frontend.git third_party/devtools-frontend',
+      {
+        cwd: projectRoot,
+        stdio: 'inherit',
+      },
+    );
+
+    // 2. Set the sparse checkout configuration
+    execSync(
+      'git sparse-checkout set --no-cone "/*" "!/*/" "/front_end/" "!/front_end/panels/" "!/front_end/ui/" "/mcp/" "/extension-api/"',
+      {
+        cwd: devtoolsFrontendDir,
+        stdio: 'inherit',
+      },
+    );
+
+    // 3. Move the submodule's .git directory to the superproject's .git/modules
+    execSync('git submodule absorbgitdirs third_party/devtools-frontend', {
       cwd: projectRoot,
       stdio: 'inherit',
     });
-  } catch (submoduleError) {
-    console.warn('git submodule update failed:', submoduleError);
-  }
 
-  if (!existsSync(mcpEntry)) {
-    console.log('Fetching devtools-frontend...');
-    try {
-      execSync(
-        'git clone --depth 1 https://github.com/ChromeDevTools/devtools-frontend.git third_party/devtools-frontend',
-        {
-          cwd: projectRoot,
-          stdio: 'inherit',
-        },
-      );
-    } catch (cloneError) {
-      console.error('Failed to clone devtools-frontend:', cloneError);
-    }
+    // 4. Update the submodule to the correct commit (this fetches the commit and only downloads the blobs for the sparse checkout)
+    execSync(
+      'git submodule update --force --checkout third_party/devtools-frontend',
+      {
+        cwd: projectRoot,
+        stdio: 'inherit',
+      },
+    );
+  } catch (error) {
+    console.error('Failed to initialize devtools-frontend:', error);
   }
 }
 

scripts/prepare.ts

@@ -135,8 +135,8 @@ chrome-devtools list_network_requests 1 --includePreservedRequests true # Includ
 chrome-devtools evaluate_script "() => document.title" --pageId 1 # Evaluate a JavaScript function on page 1
 chrome-devtools evaluate_script "(a) => a.innerText" --pageId 1 --args 1_4 # Evaluate JS with UID arguments on page 1
 chrome-devtools get_console_message 1 1 # Gets a console message by its ID
-chrome-devtools get_css_styles 1 "1_4" # Retrieves resolved CSS styles (inline, matched, inherited, pseudo) for an element on page 1
-chrome-devtools get_css_styles 1 "1_4" --pageSize 20 --pageIdx 0 # Get CSS styles with pagination on page 1
+chrome-devtools get_css_styles 1 "1_4" # Get CSS styles with pagination on page 1 (default: 10 rules, pageIdx 0)
+chrome-devtools get_css_styles 1 "1_4" --pageSize 20 --pageIdx 1 # Paginate CSS rules with custom page size and custom 0-based page index
 chrome-devtools lighthouse_audit 1 --mode "navigation" # Run Lighthouse audit for navigation
 chrome-devtools lighthouse_audit 1 --mode "snapshot" --device "mobile" # Run Lighthouse audit for a snapshot on mobile
 chrome-devtools lighthouse_audit 1 --outputDirPath ./out # Run Lighthouse audit and save reports

skills/chrome-devtools-cli/SKILL.md

@@ -34,8 +34,8 @@ Note: For `evaluate_script`, `pageId` is required when targeting pages. However,
 
 - **Automation/interaction**: `take_snapshot` (text-based, faster, better for automation)
 - **Visual inspection**: `take_screenshot` (when user needs to see visual state)
-- **CSS & Styling inspection**: Use `get_css_styles` to inspect matched rules, cascade, and CSS variables.
-- **Additional details**: Use `evaluate_script` for final resolved values (`getComputedStyle`) or runtime DOM/JS data not in the accessibility tree.
+- **CSS & Styling inspection**: Use `get_css_styles` to inspect matched rules, cascade, and CSS variables. Treat the output as authoritative and complete.
+- **Additional details**: Use `evaluate_script` for runtime DOM/JS data not available via `get_css_styles` or `take_snapshot`.
 
 ### Parallel execution