main
1020 次代码提交
| 作者 | SHA1 | 备注 | 提交日期 | |
|---|---|---|---|---|
 Alex Rudenko
|
b4546ef86b |
test: fix potential flakiness in tests (#2396)
release-please / release-please (push) Has been cancelled
Compile and run tests / Tests on macos-latest with node 22 (push) Has been cancelled
Compile and run tests / Tests on ubuntu-latest with node 22 (push) Has been cancelled
Compile and run tests / Tests on windows-latest with node 22 (push) Has been cancelled
Compile and run tests / Tests on macos-latest with node 24 (push) Has been cancelled
Compile and run tests / Tests on ubuntu-latest with node 24 (push) Has been cancelled
Compile and run tests / Tests on windows-latest with node 24 (push) Has been cancelled
Compile and run tests / Tests on macos-latest with node 26 (push) Has been cancelled
Compile and run tests / Tests on ubuntu-latest with node 26 (push) Has been cancelled
Compile and run tests / Tests on windows-latest with node 26 (push) Has been cancelled
Check code before submitting / [Required] Check correct format (push) Has been cancelled
Check code before submitting / [Required] Check docs updated (push) Has been cancelled
Compile and run tests / [Required] Tests passed (push) Has been cancelled
Assortment of various flakiness conditions found running tests in a loop locally: This PR introduces a comprehensive set of hermetic retry layers and aggressive timeout handlers across the test suite to insulate it from random Chromium startup hangs, CDP deadlocks, and Puppeteer lifecycle flakes. It guarantees that temporary browser infrastructure failures are automatically retried without failing the CI, while actual code assertion failures still fail fast. ### Test Harness & Retry Improvements • tests/utils.ts: Rewrote withBrowser to include a 30-second internal timeout and a 3-attempt retry loop. If Chromium locks up or disconnects (Target closed / socket hang up), the browser is forcibly evicted (via SIGKILL if browser.close() hangs) and the test setup is cleanly retried. • tests/index.test.ts: Wrapped withClient (used by E2E tests) in a 3-attempt retry loop to handle the daemon/Chromium hanging during launch and triggering the 60-second MCP client timeout. • tests/browser.test.ts: Added a safeClose helper that imposes a 2-second timeout before SIGKILLing browsers, and wrapped raw Puppeteer tests in runWithRetry to handle startup hangs. • tests/shutdown.test.ts: Added a setupServerWithRetry helper to prevent random 60s RPC timeouts when the server's Chrome instance hangs during boot. ### Flaky Operations & Navigation Fixes • src/tools/performance.ts & tests/tools/performance.test.ts: Replaced the notoriously flaky waitUntil: ['networkidle0'] with 'load' when navigating to about:blank in performance_start_trace. This prevents random 10-second Navigation timeout exceeded errors. Also stubbed goto in the associated unit tests for better hermeticity. • src/McpContext.ts: Wrapped browser.installExtension() with a 15-second timeout to prevent deadlocks when an extension fails to load. • tests/tools/extensions.test.ts: Removed flaky headless UI navigations to chrome://extensions in favor of using the context.listExtensions() API. • tests/tools/pages.test.js.snapshot: Synced test snapshots to reflect updated environment baselines. |
||
|
François Beaufort
|
354458e23f |
docs: Update Chrome requirement for categoryExperimentalWebmcp (#2163)
Following https://github.com/puppeteer/puppeteer/pull/15069, this PR requires Chrome 150+ with the following flag: `--enable-features=WebMCPTesting` to enable debugging WebMCP tools. |
||
|
Alex Rudenko
|
348975d808 |
refactor: clean up McpResponse.handle (#2392)
- remove unused toolName - extract helpers and fetch data in parallel |
||
|
Thomas Bachem
|
dcbaf49518 |
fix: include the tab id in get_tab_id's text response (#2381)
As discussed in #2366: `get_tab_id` gates on `--experimentalInteropTools`, but its result only went into `structuredContent`, which is dropped unless `--experimentalStructuredContent` is also set – so with interop alone the tool always returned an empty text response. This appends a `Tab ID: <id>` line to the text response and keeps `structuredContent.tabId` as-is – `key: value` so it stays trivially parseable. ## Testing The existing `returns the tab id` test asserted empty `responseLines`, which pinned the old behavior – now it asserts the `Tab ID:` line. Verified end-to-end over stdio with `--experimentalInteropTools` alone: the text response is `Tab ID: <id>` where it was `""` before. |
||
|
Nikolay Vitkov
|
71e5c59bc9 |
test: fail if file does not exist (#2369)
Given we run test locally and that this does not change often one can
just run the command once in a while to fix the local setup.
```sh
Failed tests:
✖ matches snapshot if exists (0.78188ms)
Error: THIRD_PARTY_NOTICES does not exist, run `npm ci && npm run bundle`
at TestContext.<anonymous> (file:///usr/local/google/home/nvitkov/chrome-devtools-mcp/build/tests/third_party_notices.test.js:13:19)
at Test.runInAsyncScope (node:async_hooks:227:14)
at Test.run (node:internal/test_runner/test:1325:25)
at Test.start (node:internal/test_runner/test:1191:17)
at node:internal/test_runner/test:1792:71
at node:internal/per_context/primordials:466:82
at new Promise (<anonymous>)
at new SafePromise (node:internal/per_context/primordials:435:3)
at node:internal/per_context/primordials:466:9
at Array.map (<anonymous>)
✖ THIRD_PARTY_NOTICES (1.41613ms)
'1 subtest failed'
```
|
||
|
Dominik Inführ
|
76fd242498 |
feat: Filter heap snapshot objects by native context (#2377)
get_heapsnapshot_details can filter objects in the heap snapshot by their native context. |
||
|
Nikolay Vitkov
|
77e1d3f961 | refactor: use a destructor to shorten the calls (#2376) | ||
|
Dominik Inführ
|
8432cb97a2 |
feat: Add get_heapsnapshot_object_details MCP tool (#2374)
Add a get_heapsnapshot_object_details MCP tool which lets the agent query all known information about a node in the heap snapshot. Co-authored-by: Dominik Inführ <dinfuehr@chromium.org> |
||
|
Dominik Inführ
|
f78a911dc0 |
feat: Emit native contexts in snapshot summary (#2375)
Emits native contexts and their sizes with the get_heapsnapshot_summary MCP tool. This should help the agent get an overview about which native contexts consume the most memory. Co-authored-by: Dominik Inführ <dinfuehr@chromium.org> |
||
|
dependabot[bot]
|
9a7e04daa2 |
chore(deps-dev): bump chrome-devtools-frontend from 1.0.1652307 to 1.0.1660788 in the bundled-devtools group across 1 directory (#2299)
Bumps the bundled-devtools group with 1 update in the / directory: [chrome-devtools-frontend](https://github.com/ChromeDevTools/devtools-frontend). Updates `chrome-devtools-frontend` from 1.0.1652307 to 1.0.1656897 <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/ChromeDevTools/devtools-frontend/commit/a5ae2f34eb11c5c58a460e6930b6bce270a3121b"><code>a5ae2f3</code></a> Use lit-html in ServiceWorkersView.ts</li> <li><a href="https://github.com/ChromeDevTools/devtools-frontend/commit/251a23abd90438b2f2bb33961e894fe0b4452057"><code>251a23a</code></a> Refactor ElementsPanel dependency injection and clean up DOMModel.cancelSearch</li> <li><a href="https://github.com/ChromeDevTools/devtools-frontend/commit/8382f01f7b9644b98beb1fa335fac9f511f16139"><code>8382f01</code></a> [global-state] Fix FrameManager access in DOMNode</li> <li><a href="https://github.com/ChromeDevTools/devtools-frontend/commit/78704b2ecc77051877bd7f805eed1bf6f88d0ff9"><code>78704b2</code></a> [Sheriff]: Fix a couple of flaky tests.</li> <li><a href="https://github.com/ChromeDevTools/devtools-frontend/commit/8b198ec693b44abe00d41a5bca65639bda55180b"><code>8b198ec</code></a> Roll browser-protocol and CfT</li> <li><a href="https://github.com/ChromeDevTools/devtools-frontend/commit/430a8bdfa2c06e2f4e974f0dade1e0cfd8bf4e88"><code>430a8bd</code></a> [global-state] Remove static instance from SimpleAppProvider</li> <li><a href="https://github.com/ChromeDevTools/devtools-frontend/commit/137dae29bacbf164674a578eb5592cb12308e141"><code>137dae2</code></a> [global-state] Stash CrUXManager on DevToolsContext and add to universe</li> <li><a href="https://github.com/ChromeDevTools/devtools-frontend/commit/4f881fd9caf41e7416b03397892c17e3e9f93d0a"><code>4f881fd</code></a> Update DevTools DEPS (trusted)</li> <li><a href="https://github.com/ChromeDevTools/devtools-frontend/commit/d46071e5459a66871e38b89ac11d5573ad2ed4fb"><code>d46071e</code></a> Make SourceMapCache instantiable instead of a singleton</li> <li><a href="https://github.com/ChromeDevTools/devtools-frontend/commit/466be4a9e6a4db8867f8c04e034d3383f624d99f"><code>466be4a</code></a> Roll browser-protocol and CfT</li> <li>Additional commits viewable in <a href="https://github.com/ChromeDevTools/devtools-frontend/compare/v1.0.1652307...v1.0.1656897">compare view</a></li> </ul> </details> <br /> --------- Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Nikolay Vitkov <nvitkov@chromium.org> |
||
|
Alex Rudenko
|
2d944f9f4e |
refactor: move tool groups (#2365)
Moves the getter for tool groups to McpPage. |
||
|
Alex Rudenko
|
5012b07799 |
docs: update security.md (#2362)
Clarifies the output of this server |
||
|
Alex Rudenko
|
3ee6a27100 |
fix: improve daemon lifecycle (#2360)
See b/534287578 |
||
|
browser-automation-bot
|
f621d0052f |
chore(main): release chrome-devtools-mcp 1.6.0 (#2306)
publish-on-tag / publish-to-npm (push) Has been cancelled
publish-on-tag / publish-to-mcp-registry (push) Has been cancelled
🤖 I have created a release *beep* *boop* --- ## [1.6.0](https://github.com/ChromeDevTools/chrome-devtools-mcp/compare/chrome-devtools-mcp-v1.5.0...chrome-devtools-mcp-v1.6.0) (2026-07-14) ### 🎉 Features * add experimentalGcfFormat flag for GCF-encoded tool responses ([#2235](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/2235)) ([chrome-devtools-mcp-v1.6.0 |
||
|
Serhii Zghama
|
d0025b3908 |
fix: paginate page 0 in list_network_requests and list_console_messages (#2359)
`list_network_requests` and `list_console_messages` treat an explicit
`pageIdx: 0` as "no pagination" and dump every result, while `pageIdx:
1` and up paginate correctly.
The guards in `setIncludeNetworkRequests`/`setIncludeConsoleData` build
the pagination options with `options?.pageSize || options?.pageIdx`, so
a bare `{pageIdx: 0}` collapses to `undefined` — 0 is falsy — and
`paginate()` never runs. That's a bit odd since `paginate()` already
decides for itself when there's nothing to paginate
(`noPaginationOptions` checks `pageSize === undefined && pageIdx ===
undefined`), so page 0 is a perfectly valid first page there. The memory
tools, which pass their options straight through to `paginate()`, handle
`pageIdx: 0` fine — only these two guards get it wrong, so an agent
walking pages 0, 1, 2… gets the full list on page 0 and a 20-item window
from page 1 on.
Switched both guards to an explicit `!== undefined` check so `pageIdx:
0` reaches `paginate()` and gets the default page size like every other
page. Both-omitted still short-circuits to the full list, so nothing
else changes. Added a regression test for the `{pageIdx: 0}` case.
|
||
|
mehmet turac
|
c1736a071b |
docs: update memory leak debugging skill (#2330)
## Summary - Update the memory leak debugging skill to prefer the built-in heap snapshot tools. - Add guidance for comparing snapshots, inspecting retainers, and closing loaded snapshots. - Keep memlab and the fallback comparison script as external fallback paths. Issue #2329. ## Validation - `git diff --check origin/main...HEAD` - `npm run check-format` |
||
|
Alex Rudenko
|
9c3542bd74 |
refactor: move and rename files (#2355)
- move utilities to sub-folders where applicable - changes issue-descriptions to issuesDescriptions.ts and moves it to devtools/ |
||
|
Thomas Bachem
|
3e8d92245c |
fix: keep page ids unique across browser reconnects (#2345)
Closes #2339 Reconnecting after a browser restart builds a fresh `McpContext`, which restarted the page id counter at 1 – ids from before the restart silently resolved to unrelated pages of the new browser (repro in #2339). Two changes: - The new context continues the id counter where the previous one left off (`startingPageId` option), so a stale id now fails with the existing "No page found" error and the agent re-lists - The first response after a reconnect carries a one-time note ("the browser was restarted or reconnected since the last call. Page ids have changed..."), like the #2308 fallback note. Since tool errors run through the same response formatting, the note shows up together with the very error the stale id produces Verified against the #2339 repro: the stale `select_page` now returns the note plus "No page found", and the next listing shows the new browser's pages under fresh ids. One thing I noticed but left alone: The replaced context isn't `dispose()`d on reconnect – pre-existing, and everything it holds is tied to the dead browser anyway. Happy to add that here if you'd like. |
||
|
dependabot[bot]
|
4094e8eb27 |
chore(deps-dev): bump @google/genai from 2.10.0 to 2.11.0 in the dev-dependencies group (#2350)
Bumps the dev-dependencies group with 1 update: [@google/genai](https://github.com/googleapis/js-genai). Updates `@google/genai` from 2.10.0 to 2.11.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/googleapis/js-genai/releases">@google/genai's releases</a>.</em></p> <blockquote> <h2>v2.11.0</h2> <h2><a href="https://github.com/googleapis/js-genai/compare/v2.10.0...v2.11.0">2.11.0</a> (2026-07-09)</h2> <h3>Features</h3> <ul> <li>Add environment_id in network config (<a href="https://github.com/googleapis/js-genai/commit/85fe0a5bef70c507ba8641016eca5f10359cbac1">85fe0a5</a>)</li> <li>Add response_format and Translation_config in GenerationConfig (<a href="https://github.com/googleapis/js-genai/commit/3f3b7bc5179d0252470e7a6e87519ff894464a7e">3f3b7bc</a>)</li> <li>add retrieval result step and new fields to maps and search results (<a href="https://github.com/googleapis/js-genai/commit/ecfdc69cffe071e5841c562cacac0d4574a86303">ecfdc69</a>)</li> <li>Add Tool.exa_ai_search for Gemini Enterprise API (<a href="https://github.com/googleapis/js-genai/commit/3f3b7bc5179d0252470e7a6e87519ff894464a7e">3f3b7bc</a>)</li> <li>support Function declarations during Agent Creation (<a href="https://github.com/googleapis/js-genai/commit/824badf72b009e72696e3ce5bd39d99e6f17888c">824badf</a>)</li> <li>voice consent signature types across all SDK languages. (<a href="https://github.com/googleapis/js-genai/commit/5fb5354de34e8fe394c92ad279bd07e756328005">5fb5354</a>)</li> </ul> <h3>Bug Fixes</h3> <ul> <li><strong>interactions:</strong> accept both dict and list[dict] for transform (<a href="https://github.com/googleapis/js-genai/commit/67d2f683643946e512875065f98bf9b8d628bc61">67d2f68</a>)</li> </ul> <h3>Code Refactoring</h3> <ul> <li><strong>interactions:</strong> remove cached_content, presence_penalty, and frequency_penalty; expose safety_settings and labels (<a href="https://github.com/googleapis/js-genai/commit/0f414be2babac4e5d94a23a1880b898cfc5919d4">0f414be</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/googleapis/js-genai/blob/main/CHANGELOG.md">@google/genai's changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/googleapis/js-genai/compare/v2.10.0...v2.11.0">2.11.0</a> (2026-07-09)</h2> <h3>Features</h3> <ul> <li>Add environment_id in network config (<a href="https://github.com/googleapis/js-genai/commit/85fe0a5bef70c507ba8641016eca5f10359cbac1">85fe0a5</a>)</li> <li>Add response_format and Translation_config in GenerationConfig (<a href="https://github.com/googleapis/js-genai/commit/3f3b7bc5179d0252470e7a6e87519ff894464a7e">3f3b7bc</a>)</li> <li>add retrieval result step and new fields to maps and search results (<a href="https://github.com/googleapis/js-genai/commit/ecfdc69cffe071e5841c562cacac0d4574a86303">ecfdc69</a>)</li> <li>Add Tool.exa_ai_search for Gemini Enterprise API (<a href="https://github.com/googleapis/js-genai/commit/3f3b7bc5179d0252470e7a6e87519ff894464a7e">3f3b7bc</a>)</li> <li>support Function declarations during Agent Creation (<a href="https://github.com/googleapis/js-genai/commit/824badf72b009e72696e3ce5bd39d99e6f17888c">824badf</a>)</li> <li>voice consent signature types across all SDK languages. (<a href="https://github.com/googleapis/js-genai/commit/5fb5354de34e8fe394c92ad279bd07e756328005">5fb5354</a>)</li> </ul> <h3>Bug Fixes</h3> <ul> <li><strong>interactions:</strong> accept both dict and list[dict] for transform (<a href="https://github.com/googleapis/js-genai/commit/67d2f683643946e512875065f98bf9b8d628bc61">67d2f68</a>)</li> </ul> <h3>Code Refactoring</h3> <ul> <li><strong>interactions:</strong> remove cached_content, presence_penalty, and frequency_penalty; expose safety_settings and labels (<a href="https://github.com/googleapis/js-genai/commit/0f414be2babac4e5d94a23a1880b898cfc5919d4">0f414be</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/googleapis/js-genai/commit/136ea2616b056230d48a07119e1becf3c4b4dea9"><code>136ea26</code></a> chore(main): release 2.11.0 (<a href="https://redirect.github.com/googleapis/js-genai/issues/1743">#1743</a>)</li> <li><a href="https://github.com/googleapis/js-genai/commit/3bf5090a86104ed73bb7d68207a2a3f7481b9c03"><code>3bf5090</code></a> chore: update the release.txt</li> <li><a href="https://github.com/googleapis/js-genai/commit/43c53804bf01d0f4af960c4c55efb2690b901087"><code>43c5380</code></a> chore: release 2.11.0</li> <li><a href="https://github.com/googleapis/js-genai/commit/824badf72b009e72696e3ce5bd39d99e6f17888c"><code>824badf</code></a> feat: support Function declarations during Agent Creation</li> <li><a href="https://github.com/googleapis/js-genai/commit/0f414be2babac4e5d94a23a1880b898cfc5919d4"><code>0f414be</code></a> refactor(interactions)!: remove cached_content, presence_penalty, and frequen...</li> <li><a href="https://github.com/googleapis/js-genai/commit/1127b438548009c571b26f6a30ec1409644f7f21"><code>1127b43</code></a> chore: Add multiple approval check for major releases</li> <li><a href="https://github.com/googleapis/js-genai/commit/67d2f683643946e512875065f98bf9b8d628bc61"><code>67d2f68</code></a> fix(interactions): accept both dict and list[dict] for transform</li> <li><a href="https://github.com/googleapis/js-genai/commit/5fb5354de34e8fe394c92ad279bd07e756328005"><code>5fb5354</code></a> feat: voice consent signature types across all SDK languages.</li> <li><a href="https://github.com/googleapis/js-genai/commit/aad178eda1aaf735ba8a471beb58c81eda0c8eac"><code>aad178e</code></a> chore: Remove default api-revision header</li> <li><a href="https://github.com/googleapis/js-genai/commit/be7ab10138e15046a56a6e0bae4ba8502eeefe44"><code>be7ab10</code></a> chore: sort 'properties' keys in OpenAPI schemas</li> <li>Additional commits viewable in <a href="https://github.com/googleapis/js-genai/compare/v2.10.0...v2.11.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
Alex Rudenko
|
68cfce2bcb |
refactor: clean up page snapshot generation (#2348)
- remove obsolete devtools page detection step - move isolated context processing out of the browser pages fetching - move filtering of pages out of getPages(). That should just be a getter. |
||
|
Alex Rudenko
|
c53c1ec4c9 | refactor: use response page in formatting (#2349) | ||
|
Liohtml
|
78ccb193e0 |
fix: release held modifiers when press_key key event fails (#2347)
## What
`press_key` currently presses each modifier down, presses the main key,
then releases the modifiers — in three sequential steps with no
`try/finally`:
```ts
for (const modifier of modifiers) {
await page.pptrPage.keyboard.down(modifier);
}
await page.pptrPage.keyboard.press(key); // if this rejects…
for (const modifier of modifiers.toReversed()) {
await page.pptrPage.keyboard.up(modifier); // …this never runs
}
```
If `keyboard.press(key)` rejects — a CDP hiccup, a target crash, or a
dropped connection — the release loop is skipped and the modifier keys
are left **logically held down in the browser**.
`waitForEventsAfterAction` re-throws the action error, so nothing
downstream releases them either.
This is the unpaired-`keyDown` class of defect asked about in #2309
(*"whether any code path sends a keyDown without a guaranteed matching
keyUp on an error/timeout branch"*). This PR fixes the one concrete
instance of it in this repo.
## Fix
Wrap the down/press sequence in `try/finally` and track which modifiers
were actually pressed, releasing each held modifier even when the main
press throws. Only modifiers whose `keyboard.down()` succeeded are
released, so a failure *while* pressing a modifier doesn't emit a
spurious `keyUp`.
## Test
Adds a regression test (real browser, keydown/keyup logging) that
injects a `press()` failure mid-sequence and asserts both modifiers are
still released. It fails on `main` (`['dControl','dShift']` — no keyups)
and passes with the fix (`['dControl','dShift','uShift','uControl']`).
Verified locally: full `tests/tools/input.test.ts` suite passes, `npm
run typecheck`, eslint, and prettier all clean.
## Scope note re: #2309
I want to be precise about what this does and does not address. This
closes a **browser-level** stuck-key path: leaked keys here live in
Chromium's input state (CDP `Input.dispatchKeyEvent` is injected into
the renderer), so the observable effect is a modifier stuck **within the
driven page**. The report in #2309 is a bare `Space` that repeats
**system-wide** and survives physically unplugging the keyboard — that
symptom is at the OS input layer, which CDP-injected input doesn't route
through, so I don't claim this fully explains that case (details and a
non-reboot workaround are in a comment on the issue). Still, an unpaired
keyDown on an error branch is a real defect worth closing on its own,
and it's exactly the code path the issue asked to audit.
Prepared with AI assistance (Claude Code) and verified against a local
build before submission.
|
||
|
Alex Rudenko
|
58ba174273 |
refactor: move remaining McpContext getters (#2342)
Moves various getters to McpPage. |
||
|
Thomas Bachem
|
eb049513d2 |
fix: resolve page ids only among listed pages (#2332)
Follow-up to #2304, and to #2328 which fixed the symptom. After #2333, `getPages()` – what `list_pages` presents – is a filtered view over `#mcpPages` that excludes `devtools://` frontends (unless `experimentalDevToolsDebugging` is set; they enter `#mcpPages` via `handleDevToolsAsPage`). `getPageById()` still searches all of `#mcpPages`, though – so `select_page`, and every other tool that takes a `pageId`, can target a page `list_pages` never showed. #2328 stopped that from silently stealing a still-open selection. This goes to the root: `getPageById()` now resolves through `getPages()`, so an unlisted page isn't targetable in the first place. Page ids only ever reach the client through the listing, so an unlisted id has no legitimate source. `experimentalDevToolsDebugging` is unaffected – the listing already includes devtools frontends there. All five callers (`select_page`, `close_page`, `evaluate_script`, `get_tab_id`, and the generic `pageId` handler) benefit uniformly. Also trims the now-impossible example from the fallback comment – an unlisted `devtools://` page can no longer be selected. Test: with DevTools open, the frontend page is tracked but unlisted; the new test asserts no id outside `getPages()` resolves through `getPageById()`. Refs: #2304 |
||
|
Alex Rudenko
|
c006c9ba5e | refactor: move DevTools universe to McpPage (#2341) | ||
|
Piotr Paulski
|
515f8afb58 |
chore: report exact bundled package versions during release (#2318)
At bundle time, we know exactly which version of the package is installed, we should report exact version instead of a range from package.json. This change parses package-lock.json to obtain this information. This approach aligns better with upstream security analyzers relying on dependency version information. Co-authored-by: Piotr Paulski <piotrpaulski@chromium.org> |
||
|
Alex Rudenko
|
5b33debf1a | refactor: clean up McpContext getters (#2340) | ||
|
Alex Rudenko
|
8a4ddb3256 | refactor: remove isolated context getter (#2336) | ||
|
Nikolay Vitkov
|
64005f924f |
refactor: use helper for Dialog handle (#2334)
Re-use the logic in the wait for helper to expose per dialog type handling. |
||
|
Alex Rudenko
|
9cd734b0a3 |
refactor: clean up more of the context interface (#2335)
- removed redundant page getters |
||
|
Alex Rudenko
|
16db01f79c |
refactor: clean up page management (#2333)
- remove `#pages` and Puppeteer page getters - rename methods for clarity |
||
|
Nikolay Vitkov
|
ca8d219ede |
revert: support experimental allowlist for navigate tool calls (#1935) (#2203)
This reverts commit
|
||
|
Dominik Inführ
|
15a6b789da |
feat: Print object count and total sizes in get_heapsnapshot_details (#2325)
This emits object count and total shallow sizes for get_heapsnapshot_details. |
||
|
Alex Rudenko
|
9bc61b43d6 | refactor: make collectors work per page (#2324) | ||
|
Dominik Inführ
|
2812902ba9 |
feat: Support filter with heap snapshots aggregates (#2323)
This exposes DevTools named filters in get_heapsnapshot_details and get_heapsnapshot_class_nodes tools. This allows the client to list e.g. all objects retained through detached DOM objects. Co-authored-by: Dominik Inführ <dinfuehr@chromium.org> |
||
|
Liohtml
|
c065fd90ce |
fix(telemetry): resolve enum values through nested schema wrappers (#2315)
## What
`generateToolMetrics` reads an enum parameter's values by unwrapping
**at most
one** `optional` wrapper:
```ts
if (schema._def.values?.length > 0) {
values = schema._def.values;
} else {
values = schema._def.innerType._def.values; // only one level
}
```
An enum parameter wrapped in `.default().optional()` (or any nested
`optional`/`default`/`nullable` combination) therefore falls through to
`schema._def.innerType._def.values === undefined`, and `npm run
update-metrics`
(run as part of `npm run gen`) crashes:
```
TypeError: Cannot read properties of undefined (reading '0')
at validateEnumHomogeneity (build/src/telemetry/metricsRegistry.js:12)
at generateToolMetrics (build/src/telemetry/metricsRegistry.js:59)
```
## Why it matters
`npm run gen` is required whenever a tool is added or changed (per
`CONTRIBUTING.md`). Declaring an enum parameter with a default — a
natural,
documented zod pattern — silently breaks docs/metrics generation.
## Fix
Add `getEnumValues()` in `transformation.ts` that recursively unwraps
`optional` / `default` / `nullable` / `effects` wrappers, mirroring the
existing
`getZodType()`, and use it in `generateToolMetrics`. Behavior is
unchanged for
the existing bare-enum and single-`optional` cases.
## Tests
- `getEnumValues` unit tests: bare enum, `optional`, `default`, both
orders of
`default`+`optional`, and throws for a non-enum type.
- `generateToolMetrics` regression test with
`zod.enum(...).default(...).optional()`.
- `npm run typecheck`, the telemetry tests, and `npm run check-format`
pass.
---
First-time contributor here — happy to sign the CLA.
|
||
|
Thomas Bachem
|
c645eee875 |
fix: keep a still-open selected page instead of falling back to the first page (#2328)
Follow-up to #2304. `createPagesSnapshot()` reselects `#pages[0]` whenever the selected page is missing from `#pages`, even when that page is still open. So a live selection can be silently swapped, not only a closed one. The case that hit us is a `devtools://` page: - the server connects with `handleDevToolsAsPage: true` (`src/browser.ts`), so DevTools frontends are pages and land in `#mcpPages` - `#pages` filters `devtools://` out (`src/McpContext.ts`, unless `experimentalDevToolsDebugging` is set) - `getPageById()` (used by `select_page`) reads `#mcpPages`, not `#pages`, so a devtools page can be selected even though `list_pages` never lists it - the next snapshot finds it missing from `#pages` and, because the fallback keys on `#pages` membership rather than `isClosed()`, reselects `#pages[0]` with the page still open (`isClosed() === false`) This reproduces on a normal Chrome (details and a repro in #2304). This change gates the fallback on `isClosed()`, as proposed in #2304. A still-open selection is kept; a genuinely closed page still auto-advances, so the browser-like behavior for closed tabs is unchanged. One consequence: the "is no longer listed" wording added in #2308 becomes unreachable, since a live page missing from the list no longer triggers a fallback. I left it in place to keep this diff focused, but I'm happy to simplify it here or in a follow-up. The unit test that covered the missing-but-open case now asserts the selection is retained. Refs: #2304 |
||
|
Dominik Inführ
|
ed7e95d3e0 | fix: Wait until daemon is started (#2327) | ||
|
herdiyanitdev
|
6e56c028cf |
feat: support --allow-unrestricted-paths configuration (#2296)
## Summary validatePath() in McpContext returned immediately, with no restriction at all, whenever roots() returned undefined. roots() only returns undefined when the connecting MCP client never negotiates the optional roots capability during initialize, which any minimal client can trigger simply by omitting it from its declared capabilities. Since roots() already always appends the OS temp directory to whatever explicit roots are configured, this change makes it return that same default (temp directory only) instead of undefined when no roots have been set. This removes the early return in validatePath() entirely, so path validation now runs unconditionally rather than being conditional on whether the connecting client happened to negotiate a capability it was never required to declare per the MCP spec. Any filePath-accepting tool (take_screenshot, saveFile, and the performance/Lighthouse export tools that route through the same check) had its only path-traversal guard silently disabled for the lifetime of a connection whenever the client omitted the optional roots capability. Since this server is designed to let an LLM drive a browser, and browsed page content is not trusted input, this meant a client that simply doesn't implement roots (a plausible, non-adversarial default for lightweight or custom MCP clients) removed the only boundary preventing the connected agent from writing to any path the process can reach. Added a test that exercises the actual default state of roots (never calling setRoots()) directly, since the existing tests always call setRoots(), even with an empty array, before validating. Verified locally with a minimal MCP client that declares no capabilities: before this change, take_screenshot with a filePath outside any root wrote a real file to an arbitrary path with no error; after this change, the same call is rejected with the existing Access denied error. Also verified that a client that does declare roots is unaffected, and that writes to the OS temp directory continue to succeed with no roots negotiated, matching prior behavior for that path. |
||
|
Dominik Inführ
|
ff53b7bb82 |
refactor: Use array instead of Map for idToClassKey (#2321)
Switches idToClassKey to an array since ids are strictly incremented from 1. This also allows us to drop the id generator use. Co-authored-by: Dominik Inführ <dinfuehr@chromium.org> |
||
|
Natasha Gorshunova
|
a8c7c73ca5 |
chore: add dependabot cooldown option (#2320)
Co-authored-by: Natallia Harshunova <nharshunova@chromium.org> |
||
|
Thomas Bachem
|
2c16ac311b |
fix: report when the selected page was auto-replaced by the fallback (#2308)
Follow-up to #2304 (the "note" part discussed there). When the selected page disappears from the page list, `createPagesSnapshot()` silently re-selects the first page. The agent gets no signal: if its next call is `list_pages` (which is what the closed-page error message recommends), the listing already shows the new selection and every subsequent tool call runs against a page the agent never picked. This PR records the automatic fallback and surfaces it as a one-line note in the pages section of the same response: ``` ## Pages Note: the previously selected page was closed. Page 1 is now selected. 1: about:blank [selected] ``` For a selected page that is missing from the list without being closed, the note reads "is no longer listed" instead. If the expectation from #2304 holds (a page stays listed as long as it is not closed), that wording never renders; if the transient case discussed there does occur in the wild, the note will make it visible. The fallback behavior itself is unchanged (as discussed in #2304, closed tabs keep the browser-like auto-selection). No note is emitted on first connect, when nothing was selected before. Tests: two unit tests for the fallback bookkeeping (closed page, regular selection), one for the missing-but-open case via a stubbed page list, and the one affected snapshot updated (`close_page` now includes the note). Refs: #2304 |
||
|
Alex Rudenko
|
ffc6060acf |
feat: update Lighthouse to 13.4.0 (#2317)
See https://github.com/GoogleChrome/lighthouse/releases/tag/v13.4.0 |
||
|
Nikolay Vitkov
|
b2c63e644e |
perf: concurrent I/O in Root Path Resolution (#2279)
💡 **What:** Modified `McpContext.validatePath` to resolve the absolute paths for all configured workspace roots concurrently using `Promise.allSettled`, replacing the previous sequential iteration. 🎯 **Why:** The previous implementation executed potentially expensive disk I/O operations (`fs.realpath()`) synchronously one-by-one in a `for...of` loop. This caused a performance bottleneck when a user had several configured roots or during heavy file load activity, as each root had to fully resolve before proceeding to the next. 📊 **Measured Improvement:** Measured with 10 workspace roots (where only the last one matches). The change reduced execution time for a 1,000-iteration micro-benchmark from ~1,350ms to ~400ms, yielding a 70% speedup in this code path. --- *PR created automatically by Jules for task [14748109266156669449](https://jules.google.com/task/14748109266156669449) started by @Lightning00Blade* Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> |
||
|
dependabot[bot]
|
74cea492b6 |
chore(deps-dev): bump puppeteer from 25.2.1 to 25.3.0 in the bundled group (#2300)
Bumps the bundled group with 1 update: [puppeteer](https://github.com/puppeteer/puppeteer). Updates `puppeteer` from 25.2.1 to 25.3.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/puppeteer/puppeteer/releases">puppeteer's releases</a>.</em></p> <blockquote> <h2>puppeteer-core: v25.3.0</h2> <h2><a href="https://github.com/puppeteer/puppeteer/compare/puppeteer-core-v25.2.1...puppeteer-core-v25.3.0">25.3.0</a> (2026-07-01)</h2> <h3>🎉 Features</h3> <ul> <li>support installing extensions for browser contexts (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15164">#15164</a>) (<a href="https://github.com/puppeteer/puppeteer/commit/118d84d2622306f1b9e85ed9acee22b2931f12c7">118d84d</a>)</li> </ul> <h3>🛠️ Fixes</h3> <ul> <li>handle swaps without a timer (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15198">#15198</a>) (<a href="https://github.com/puppeteer/puppeteer/commit/2356a15404acca1e00243a4f72408ecdb916ac11">2356a15</a>)</li> <li>normalize duplicate set-cookie headers using newline (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15173">#15173</a>) (<a href="https://github.com/puppeteer/puppeteer/commit/55787d515570109ba7e5cb97df18499d743923fb">55787d5</a>)</li> <li>roll to Firefox 152.0.3 (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15158">#15158</a>) (<a href="https://github.com/puppeteer/puppeteer/commit/2d648522d4a90ed7fc5c79e6298f36f0dc0781f4">2d64852</a>)</li> <li>roll to Firefox 152.0.4 (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15195">#15195</a>) (<a href="https://github.com/puppeteer/puppeteer/commit/d382a218051c323e1d4d4d1a528c53370a6b1ee7">d382a21</a>)</li> </ul> <h3>📄 Documentation</h3> <ul> <li>fix the typos on documentation (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15167">#15167</a>) (<a href="https://github.com/puppeteer/puppeteer/commit/ab74e6a6720ec05768979e3c2d9b26bcb5cd763f">ab74e6a</a>)</li> </ul> <h3>Dependencies</h3> <ul> <li>The following workspace dependencies were updated <ul> <li>dependencies <ul> <li><code>@puppeteer/browsers</code> bumped from 3.0.5 to 3.0.6</li> </ul> </li> </ul> </li> </ul> <h2>puppeteer: v25.3.0</h2> <h2><a href="https://github.com/puppeteer/puppeteer/compare/puppeteer-v25.2.1...puppeteer-v25.3.0">25.3.0</a> (2026-07-01)</h2> <h3>♻️ Chores</h3> <ul> <li><strong>puppeteer:</strong> Synchronize puppeteer versions</li> </ul> <h3>Dependencies</h3> <ul> <li>The following workspace dependencies were updated <ul> <li>dependencies <ul> <li><code>@puppeteer/browsers</code> bumped from 3.0.5 to 3.0.6</li> <li>puppeteer-core bumped from 25.2.1 to 25.3.0</li> </ul> </li> </ul> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/puppeteer/puppeteer/blob/main/CHANGELOG.md">puppeteer's changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/puppeteer/puppeteer/compare/puppeteer-v25.2.1...puppeteer-v25.3.0">25.3.0</a> (2026-07-01)</h2> <h3>♻️ Chores</h3> <ul> <li><strong>puppeteer:</strong> Synchronize puppeteer versions</li> </ul> <h3>Dependencies</h3> <ul> <li>The following workspace dependencies were updated <ul> <li>dependencies <ul> <li><code>@puppeteer/browsers</code> bumped from 3.0.5 to 3.0.6</li> </ul> </li> </ul> </li> </ul> <h3>🎉 Features</h3> <ul> <li>support installing extensions for browser contexts (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15164">#15164</a>) (<a href="https://github.com/puppeteer/puppeteer/commit/118d84d2622306f1b9e85ed9acee22b2931f12c7">118d84d</a>)</li> </ul> <h3>🛠️ Fixes</h3> <ul> <li>handle swaps without a timer (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15198">#15198</a>) (<a href="https://github.com/puppeteer/puppeteer/commit/2356a15404acca1e00243a4f72408ecdb916ac11">2356a15</a>)</li> <li>normalize duplicate set-cookie headers using newline (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15173">#15173</a>) (<a href="https://github.com/puppeteer/puppeteer/commit/55787d515570109ba7e5cb97df18499d743923fb">55787d5</a>)</li> <li>roll to Firefox 152.0.3 (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15158">#15158</a>) (<a href="https://github.com/puppeteer/puppeteer/commit/2d648522d4a90ed7fc5c79e6298f36f0dc0781f4">2d64852</a>)</li> <li>roll to Firefox 152.0.4 (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15195">#15195</a>) (<a href="https://github.com/puppeteer/puppeteer/commit/d382a218051c323e1d4d4d1a528c53370a6b1ee7">d382a21</a>)</li> </ul> <h3>📄 Documentation</h3> <ul> <li>fix the typos on documentation (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15167">#15167</a>) (<a href="https://github.com/puppeteer/puppeteer/commit/ab74e6a6720ec05768979e3c2d9b26bcb5cd763f">ab74e6a</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/puppeteer/puppeteer/commit/58d9b023ed74c3a1f14ec5fd9315872602270c72"><code>58d9b02</code></a> chore: release main (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15165">#15165</a>)</li> <li><a href="https://github.com/puppeteer/puppeteer/commit/d382a218051c323e1d4d4d1a528c53370a6b1ee7"><code>d382a21</code></a> fix: roll to Firefox 152.0.4 (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15195">#15195</a>)</li> <li><a href="https://github.com/puppeteer/puppeteer/commit/2356a15404acca1e00243a4f72408ecdb916ac11"><code>2356a15</code></a> fix: handle swaps without a timer (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15198">#15198</a>)</li> <li><a href="https://github.com/puppeteer/puppeteer/commit/537232e28297c38023cd4f56db4d110f31cc9e08"><code>537232e</code></a> chore(webmcp): Clean unnecessary Protocol interfaces (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15199">#15199</a>)</li> <li><a href="https://github.com/puppeteer/puppeteer/commit/ab74e6a6720ec05768979e3c2d9b26bcb5cd763f"><code>ab74e6a</code></a> docs: fix the typos on documentation (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15167">#15167</a>)</li> <li><a href="https://github.com/puppeteer/puppeteer/commit/9560bcfceb4445db889abb7b735177e13b46eb3a"><code>9560bcf</code></a> chore(deps-dev): bump the dev-dependencies group across 1 directory with 20 u...</li> <li><a href="https://github.com/puppeteer/puppeteer/commit/04a95878db8eec2263d895fed2e98180a158ec76"><code>04a9587</code></a> refactor: extract zip archives with yauzl instead of CLI tools (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15085">#15085</a>)</li> <li><a href="https://github.com/puppeteer/puppeteer/commit/54143a6c9aacd788679e42ee989e796c69bcff18"><code>54143a6</code></a> chore: fix the typos on the code test and API documentation (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15169">#15169</a>)</li> <li><a href="https://github.com/puppeteer/puppeteer/commit/55787d515570109ba7e5cb97df18499d743923fb"><code>55787d5</code></a> fix: normalize duplicate set-cookie headers using newline (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15173">#15173</a>)</li> <li><a href="https://github.com/puppeteer/puppeteer/commit/118d84d2622306f1b9e85ed9acee22b2931f12c7"><code>118d84d</code></a> feat: support installing extensions for browser contexts (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/15164">#15164</a>)</li> <li>Additional commits viewable in <a href="https://github.com/puppeteer/puppeteer/compare/puppeteer-v25.2.1...puppeteer-v25.3.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Natasha Gorshunova <47688881+nattallius@users.noreply.github.com> |
||
|
dependabot[bot]
|
e17c7cbdc1 |
chore(deps-dev): bump the dev-dependencies group with 6 updates (#2298)
Bumps the dev-dependencies group with 6 updates: | Package | From | To | | --- | --- | --- | | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `26.0.1` | `26.1.0` | | [@types/sinon](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/sinon) | `21.0.1` | `22.0.0` | | [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) | `8.62.0` | `8.62.1` | | [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser) | `8.62.0` | `8.62.1` | | [prettier](https://github.com/prettier/prettier) | `3.9.3` | `3.9.4` | | [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/typescript-eslint) | `8.62.0` | `8.62.1` | Updates `@types/node` from 26.0.1 to 26.1.0 <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node">compare view</a></li> </ul> </details> <br /> Updates `@types/sinon` from 21.0.1 to 22.0.0 <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/sinon">compare view</a></li> </ul> </details> <br /> Updates `@typescript-eslint/eslint-plugin` from 8.62.0 to 8.62.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/typescript-eslint/typescript-eslint/releases">@typescript-eslint/eslint-plugin's releases</a>.</em></p> <blockquote> <h2>v8.62.1</h2> <h2>8.62.1 (2026-06-29)</h2> <h3>🩹 Fixes</h3> <ul> <li><strong>eslint-plugin:</strong> [prefer-optional-chain] use suggestion instead of autofix for trailing binary operator (<a href="https://redirect.github.com/typescript-eslint/typescript-eslint/pull/12328">#12328</a>)</li> <li><strong>eslint-plugin:</strong> [no-unnecessary-boolean-literal-compare] preserve boolean result in fixer for nullable true comparisons (<a href="https://redirect.github.com/typescript-eslint/typescript-eslint/pull/12365">#12365</a>)</li> <li><strong>eslint-plugin:</strong> [no-unnecessary-type-assertion] parenthesize object literal at left edge of expression statement (<a href="https://redirect.github.com/typescript-eslint/typescript-eslint/pull/12443">#12443</a>, <a href="https://redirect.github.com/typescript-eslint/typescript-eslint/issues/12418">#12418</a>)</li> </ul> <h3>❤️ Thank You</h3> <ul> <li>Kirk Waiblinger <a href="https://github.com/kirkwaiblinger"><code>@kirkwaiblinger</code></a></li> <li>mdm317</li> <li>Patrick Aleite</li> <li>송재욱</li> </ul> <p>See <a href="https://github.com/typescript-eslint/typescript-eslint/releases/tag/v8.62.1">GitHub Releases</a> for more information.</p> <p>You can read about our <a href="https://typescript-eslint.io/users/versioning">versioning strategy</a> and <a href="https://typescript-eslint.io/users/releases">releases</a> on our website.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/CHANGELOG.md">@typescript-eslint/eslint-plugin's changelog</a>.</em></p> <blockquote> <h2>8.62.1 (2026-06-29)</h2> <h3>🩹 Fixes</h3> <ul> <li><strong>eslint-plugin:</strong> [no-unnecessary-type-assertion] parenthesize object literal at left edge of expression statement (<a href="https://redirect.github.com/typescript-eslint/typescript-eslint/pull/12443">#12443</a>, <a href="https://redirect.github.com/typescript-eslint/typescript-eslint/issues/12418">#12418</a>)</li> <li><strong>eslint-plugin:</strong> [no-unnecessary-boolean-literal-compare] preserve boolean result in fixer for nullable true comparisons (<a href="https://redirect.github.com/typescript-eslint/typescript-eslint/pull/12365">#12365</a>)</li> <li><strong>eslint-plugin:</strong> [prefer-optional-chain] use suggestion instead of autofix for trailing binary operator (<a href="https://redirect.github.com/typescript-eslint/typescript-eslint/pull/12328">#12328</a>)</li> </ul> <h3>❤️ Thank You</h3> <ul> <li>Kirk Waiblinger <a href="https://github.com/kirkwaiblinger"><code>@kirkwaiblinger</code></a></li> <li>mdm317</li> <li>Patrick Aleite</li> <li>송재욱</li> </ul> <p>See <a href="https://github.com/typescript-eslint/typescript-eslint/releases/tag/v8.62.1">GitHub Releases</a> for more information.</p> <p>You can read about our <a href="https://typescript-eslint.io/users/versioning">versioning strategy</a> and <a href="https://typescript-eslint.io/users/releases">releases</a> on our website.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/typescript-eslint/typescript-eslint/commit/3ea32f4ba5e196c08c6da1095619d7f65ba4905e"><code>3ea32f4</code></a> chore(release): publish 8.62.1</li> <li><a href="https://github.com/typescript-eslint/typescript-eslint/commit/4ecca6d3f9ee1ab6468c8e9d6810ccc1c2f6bcf9"><code>4ecca6d</code></a> fix(eslint-plugin): [no-unnecessary-type-assertion] parenthesize object liter...</li> <li><a href="https://github.com/typescript-eslint/typescript-eslint/commit/f3a7ec78bf07b42a7e03f2091c98513e05310891"><code>f3a7ec7</code></a> chore(eslint-plugin-internal): [no-dynamic-tests] restrict where noFormat can...</li> <li><a href="https://github.com/typescript-eslint/typescript-eslint/commit/301f350cd11fecce4940b5be8a2b1146a9c6d58b"><code>301f350</code></a> fix(eslint-plugin): [no-unnecessary-boolean-literal-compare] preserve boolean...</li> <li><a href="https://github.com/typescript-eslint/typescript-eslint/commit/ebce2d40f83194599bc3022032ef4fa857977105"><code>ebce2d4</code></a> fix(eslint-plugin): [prefer-optional-chain] use suggestion instead of autofix...</li> <li>See full diff in <a href="https://github.com/typescript-eslint/typescript-eslint/commits/v8.62.1/packages/eslint-plugin">compare view</a></li> </ul> </details> <br /> Updates `@typescript-eslint/parser` from 8.62.0 to 8.62.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/typescript-eslint/typescript-eslint/releases">@typescript-eslint/parser's releases</a>.</em></p> <blockquote> <h2>v8.62.1</h2> <h2>8.62.1 (2026-06-29)</h2> <h3>🩹 Fixes</h3> <ul> <li><strong>eslint-plugin:</strong> [prefer-optional-chain] use suggestion instead of autofix for trailing binary operator (<a href="https://redirect.github.com/typescript-eslint/typescript-eslint/pull/12328">#12328</a>)</li> <li><strong>eslint-plugin:</strong> [no-unnecessary-boolean-literal-compare] preserve boolean result in fixer for nullable true comparisons (<a href="https://redirect.github.com/typescript-eslint/typescript-eslint/pull/12365">#12365</a>)</li> <li><strong>eslint-plugin:</strong> [no-unnecessary-type-assertion] parenthesize object literal at left edge of expression statement (<a href="https://redirect.github.com/typescript-eslint/typescript-eslint/pull/12443">#12443</a>, <a href="https://redirect.github.com/typescript-eslint/typescript-eslint/issues/12418">#12418</a>)</li> </ul> <h3>❤️ Thank You</h3> <ul> <li>Kirk Waiblinger <a href="https://github.com/kirkwaiblinger"><code>@kirkwaiblinger</code></a></li> <li>mdm317</li> <li>Patrick Aleite</li> <li>송재욱</li> </ul> <p>See <a href="https://github.com/typescript-eslint/typescript-eslint/releases/tag/v8.62.1">GitHub Releases</a> for more information.</p> <p>You can read about our <a href="https://typescript-eslint.io/users/versioning">versioning strategy</a> and <a href="https://typescript-eslint.io/users/releases">releases</a> on our website.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md">@typescript-eslint/parser's changelog</a>.</em></p> <blockquote> <h2>8.62.1 (2026-06-29)</h2> <p>This was a version bump only for parser to align it with other projects, there were no code changes.</p> <p>See <a href="https://github.com/typescript-eslint/typescript-eslint/releases/tag/v8.62.1">GitHub Releases</a> for more information.</p> <p>You can read about our <a href="https://typescript-eslint.io/users/versioning">versioning strategy</a> and <a href="https://typescript-eslint.io/users/releases">releases</a> on our website.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/typescript-eslint/typescript-eslint/commit/3ea32f4ba5e196c08c6da1095619d7f65ba4905e"><code>3ea32f4</code></a> chore(release): publish 8.62.1</li> <li>See full diff in <a href="https://github.com/typescript-eslint/typescript-eslint/commits/v8.62.1/packages/parser">compare view</a></li> </ul> </details> <br /> Updates `prettier` from 3.9.3 to 3.9.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/prettier/prettier/releases">prettier's releases</a>.</em></p> <blockquote> <h2>3.9.4</h2> <ul> <li>Angular: Format <code>@content(name)</code> -> <code>@content (name)</code> to align with other block syntax (<a href="https://redirect.github.com/prettier/prettier/pull/19499">#19499</a> by <a href="https://github.com/fisker"><code>@fisker</code></a>)</li> </ul> <p>🔗 <a href="https://github.com/prettier/prettier/blob/3.9.4/CHANGELOG.md#394">Changelog</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md">prettier's changelog</a>.</em></p> <blockquote> <h1>3.9.4</h1> <p><a href="https://github.com/prettier/prettier/compare/3.9.3...3.9.4">diff</a></p> <h4>Angular: Format <code>@content(name)</code> -> <code>@content (name)</code> to align with other block syntax (<a href="https://redirect.github.com/prettier/prettier/pull/19499">#19499</a> by <a href="https://github.com/fisker"><code>@fisker</code></a>)</h4> <!-- raw HTML omitted --> <pre lang="html"><code><!-- Input --> <FancyButton [label]="title"> @content (icon) { <span>Icon!</span> } @content (description) { <span>Description text</span> } <span>Other children</span> </FancyButton> <p><!-- Prettier 3.9.3 --> <FancyButton [label]="title"> <a href="https://github.com/content"><code>@content</code></a>(icon) { <span>Icon!</span> } <a href="https://github.com/content"><code>@content</code></a>(description) { <span>Description text</span> } <span>Other children</span> </FancyButton></p> <p><!-- Prettier 3.9.4 --> <FancyButton [label]="title"> <a href="https://github.com/content"><code>@content</code></a> (icon) { <span>Icon!</span> } <a href="https://github.com/content"><code>@content</code></a> (description) { <span>Description text</span> } <span>Other children</span> </FancyButton> </code></pre></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/prettier/prettier/commit/b693cb22b412b759784bc2298fc86880e351cd3a"><code>b693cb2</code></a> Release 3.9.4</li> <li><a href="https://github.com/prettier/prettier/commit/2e92ac0ee29fb83b7ce32277cb914c2eee192955"><code>2e92ac0</code></a> Angular: Format <code>@content(name)</code> -> <code>@content (name)</code> to align with other blo...</li> <li><a href="https://github.com/prettier/prettier/commit/abed2c22db3cb61e922b7284c3b6c65424353ac2"><code>abed2c2</code></a> Bump Prettier dependency to 3.9.3</li> <li><a href="https://github.com/prettier/prettier/commit/6cfbc00921de451e918b18bb5ab6b80e80f5cd34"><code>6cfbc00</code></a> Clean changelog_unreleased</li> <li>See full diff in <a href="https://github.com/prettier/prettier/compare/3.9.3...3.9.4">compare view</a></li> </ul> </details> <br /> Updates `typescript-eslint` from 8.62.0 to 8.62.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/typescript-eslint/typescript-eslint/releases">typescript-eslint's releases</a>.</em></p> <blockquote> <h2>v8.62.1</h2> <h2>8.62.1 (2026-06-29)</h2> <h3>🩹 Fixes</h3> <ul> <li><strong>eslint-plugin:</strong> [prefer-optional-chain] use suggestion instead of autofix for trailing binary operator (<a href="https://redirect.github.com/typescript-eslint/typescript-eslint/pull/12328">#12328</a>)</li> <li><strong>eslint-plugin:</strong> [no-unnecessary-boolean-literal-compare] preserve boolean result in fixer for nullable true comparisons (<a href="https://redirect.github.com/typescript-eslint/typescript-eslint/pull/12365">#12365</a>)</li> <li><strong>eslint-plugin:</strong> [no-unnecessary-type-assertion] parenthesize object literal at left edge of expression statement (<a href="https://redirect.github.com/typescript-eslint/typescript-eslint/pull/12443">#12443</a>, <a href="https://redirect.github.com/typescript-eslint/typescript-eslint/issues/12418">#12418</a>)</li> </ul> <h3>❤️ Thank You</h3> <ul> <li>Kirk Waiblinger <a href="https://github.com/kirkwaiblinger"><code>@kirkwaiblinger</code></a></li> <li>mdm317</li> <li>Patrick Aleite</li> <li>송재욱</li> </ul> <p>See <a href="https://github.com/typescript-eslint/typescript-eslint/releases/tag/v8.62.1">GitHub Releases</a> for more information.</p> <p>You can read about our <a href="https://typescript-eslint.io/users/versioning">versioning strategy</a> and <a href="https://typescript-eslint.io/users/releases">releases</a> on our website.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-eslint/CHANGELOG.md">typescript-eslint's changelog</a>.</em></p> <blockquote> <h2>8.62.1 (2026-06-29)</h2> <p>This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.</p> <p>See <a href="https://github.com/typescript-eslint/typescript-eslint/releases/tag/v8.62.1">GitHub Releases</a> for more information.</p> <p>You can read about our <a href="https://typescript-eslint.io/users/versioning">versioning strategy</a> and <a href="https://typescript-eslint.io/users/releases">releases</a> on our website.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/typescript-eslint/typescript-eslint/commit/3ea32f4ba5e196c08c6da1095619d7f65ba4905e"><code>3ea32f4</code></a> chore(release): publish 8.62.1</li> <li>See full diff in <a href="https://github.com/typescript-eslint/typescript-eslint/commits/v8.62.1/packages/typescript-eslint">compare view</a></li> </ul> </details> <br /> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
Georgii Perepechko
|
aa4be07f7a |
docs: add Grok Build CLI configuration section (#2294)
# Summary adds Grok Build CLI to the MCP client configuration list in README.md # Verification Verified visually + git diff |
||
|
Dayna Blackwell
|
3d2138945c |
feat: add experimentalGcfFormat flag for GCF-encoded tool responses (#2235)
## Summary Add `--experimentalGcfFormat` as a hidden experimental flag alongside the existing `--experimentalToonFormat`. When enabled, tool responses encode structured data using GCF (Graph Compact Format) instead of formatted JSON. No changes to existing behavior or default output. ## Why ### Benchmarked on Chrome DevTools data shapes Data shapes verified from source code and test snapshots (`ConsoleMessageConcise`, `NetworkRequestConcise`, `HeapSnapshotFormatter.toJSON()`, `SnapshotFormatter.toJSON()`): | Dataset | JSON | TOON | GCF | TOON vs JSON | GCF vs JSON | GCF vs TOON | |---------|------|------|-----|-------------|-------------|-------------| | Console (100) | 2,534 | 1,716 | 1,663 | 32.3% | 34.4% | +3.1% | | Console (500) | 12,879 | 8,761 | 8,475 | 32.0% | 34.2% | +3.3% | | Network (100) | 3,287 | 1,776 | 1,682 | 46.0% | 48.8% | +5.3% | | Network (500) | 16,547 | 8,936 | 8,442 | 46.0% | 49.0% | +5.5% | | Heap (100) | 2,210 | 797 | 753 | 63.9% | 65.9% | +5.5% | | DOM (3x3) | 282 | 295 | 244 | -4.6% | 13.5% | +17.3% | | DOM (4x3) | 396 | 464 | 407 | -17.2% | -2.8% | +12.3% | TOON increases token count on DOM snapshots (-4.6% to -17.2% vs JSON). GCF saves tokens on every data type. ### Console message corruption TOON's decoder crashes on console messages containing bracket-colon patterns, which are standard browser output: ``` [Error]: net::ERR_CONNECTION_REFUSED [React DevTools]: Component rendered 3 times [Violation]: Forced reflow while executing JavaScript took 42ms [Performance]: Long task detected (duration: 234ms) ``` 10 of 20 console messages fail TOON round-trip. GCF: zero failures. While Chrome DevTools MCP encodes only (no decode), the structurally ambiguous output can affect downstream consumers. ### LLM comprehension GCF scores 100% on general structured data and 90.7% on adversarial payloads across GPT-4o, GPT-5.5, Claude, and Gemini. JSON scores 53.6%. TOON scores 68.5%. (1,700+ evaluations.) Full eval data: [GCF benchmarks](https://gcformat.com/guide/benchmarks) ### Data integrity GCF verified lossless across 43 billion+ round-trips in 5 formats and 6 languages. Zero failures. Zero runtime dependencies. ## Implementation Mirrors the existing `experimentalToonFormat` pattern exactly: - Hidden boolean CLI flag, defaults to false - `useGcf` parameter threaded through `handle()` → `format()` - `compactEncode` helper selects GCF, TOON, or null (formatted JSON) - GCF takes precedence if both flags are set ## Changes | File | Change | |------|--------| | `src/bin/chrome-devtools-mcp-cli-options.ts` | Add `experimentalGcfFormat` flag | | `src/third_party/index.ts` | Export `gcfEncode` from `@blackwell-systems/gcf` | | `src/McpResponse.ts` | Add `useGcf` parameter, `compactEncode` helper | | `src/ToolHandler.ts` | Pass `experimentalGcfFormat` to `handle()` | | `package.json` | Add `@blackwell-systems/gcf` (pinned 2.1.2, zero deps) | ## Links - GCF spec: https://gcformat.com - TypeScript SDK: https://www.npmjs.com/package/@blackwell-systems/gcf - Benchmarks: https://gcformat.com/guide/benchmarks - Lossless verification: https://gcformat.com/guide/lossless-verification --------- Co-authored-by: Piotr Paulski <piotrpaulski@chromium.org> |
||
|
Alex Rudenko
|
b06e39b164 |
fix: enforce .gz instead of json.gz in performance tools (#2305)
Closes https://github.com/ChromeDevTools/chrome-devtools-mcp/pull/2303 |
||
|
Alex Rudenko
|
b703f2ce20 |
fix(snapshot): resolve element ids on the correct snapshot (#2295)
closes https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/2243 This probably regressed with the addition of third party developer tools because the resolveCdpElementId was not moved from page to TextSnapshot. |