Skip to content

chore: sync upstream to chrome-devtools-mcp v0.24.0 + release 0.4.0#2008

Closed
triuzzi wants to merge 9 commits into
ChromeDevTools:mainfrom
triuzzi:chore/sync-upstream-v0.24.0
Closed

chore: sync upstream to chrome-devtools-mcp v0.24.0 + release 0.4.0#2008
triuzzi wants to merge 9 commits into
ChromeDevTools:mainfrom
triuzzi:chore/sync-upstream-v0.24.0

Conversation

@triuzzi

@triuzzi triuzzi commented May 7, 2026

Copy link
Copy Markdown

Summary

  • Rebases Brave commits on top of upstream chrome-devtools-mcp v0.24.0 (22 new upstream commits pulled in).
  • Bumps Brave fork to 0.4.0 (already published to npm as brave-mcp@0.4.0).
  • Adapts upstream's env-var refactor (fix: make sure env variables are consistently applied when parsing args #1994) to use BRAVE_DEVTOOLS_MCP_NO_USAGE_STATISTICS and renames stale chrome-devtools-mcp-cli-options imports + CHROME_DEVTOOLS_MCP_* env-var refs in newly-merged test files.

Notable upstream changes

  • feat: support third-party developer tools (#1982)
  • feat: agentic browsing in lighthouse (#1931)
  • feat(cli): generate commands for conditional tools (#1962)
  • fix: handle errors due to open dialogs during tool calls (#1953) + fix: add proactive tool rejection when dialog is open #1978 + tests test: add tests for checking behavior when dialog is open #1977
  • fix(input): stop native select option clicks from timing out (#1960)
  • fix: make sure env variables are consistently applied when parsing args (#1994)
  • build: fix npm start (#1980) (kept pointing at brave-devtools-mcp.js)
  • chrome-devtools-mcp v0.24.0 release commit
  • Dep bumps: chrome-devtools-frontend → 1.0.1625079, lighthouse → 13.2.0, puppeteer → 24.43.0, @paulirish/trace_engine → 0.0.64; tiktoken removed

Test plan

  • npm run build
  • npm run typecheck
  • npm run test:no-build (after clean rebuild to clear stale inPage.* artifacts from upstream's removed feature)
  • npm publishbrave-mcp@0.4.0 live on npm
  • After merge: tag v0.4.0 and cut a GitHub release

🤖 Generated with Claude Code

triuzzi and others added 9 commits May 6, 2026 15:32
Co-Authored-By: Giancarlo Sorrentino <57813140+SirGian99@users.noreply.github.com>
* docs: rebrand CLI guide for Brave

* 0.2.1
Co-Authored-By: Claude <noreply@anthropic.com>
Updates remaining chrome-devtools references missed during the Brave
port to point at the renamed brave-devtools binaries and env vars,
and refreshes the third-party notices snapshot after recent dep bumps.

- tests/utils.ts: CLI_PATH points to build/src/bin/brave-devtools.js
- tests/check-for-updates.test.ts: BRAVE_DEVTOOLS_MCP_NO_UPDATE_CHECKS
- tests/tools/{screencast,pagesNavigateAllowlist}.test.ts:
  import ParsedArguments from brave-devtools-mcp-cli-options
- scripts/{generate-docs,generate-cli,eval_gemini}.ts: spawn
  build/src/bin/brave-devtools-mcp.js
- tests/third_party_notices.test.js.snapshot: regenerated

Co-authored-by: Claude <noreply@anthropic.com>
* fix: replace stale chrome-devtools refs in tests and scripts

Updates remaining chrome-devtools references missed during the Brave
port to point at the renamed brave-devtools binaries and env vars,
and refreshes the third-party notices snapshot after recent dep bumps.

- tests/utils.ts: CLI_PATH points to build/src/bin/brave-devtools.js
- tests/check-for-updates.test.ts: BRAVE_DEVTOOLS_MCP_NO_UPDATE_CHECKS
- tests/tools/{screencast,pagesNavigateAllowlist}.test.ts:
  import ParsedArguments from brave-devtools-mcp-cli-options
- scripts/{generate-docs,generate-cli,eval_gemini}.ts: spawn
  build/src/bin/brave-devtools-mcp.js
- tests/third_party_notices.test.js.snapshot: regenerated

Co-Authored-By: Claude <noreply@anthropic.com>

* chore: release 0.3.0

Bumps the package, server, plugin, and runtime VERSION to 0.3.0 to
mark the upstream sync to chrome-devtools-mcp 0.23.0 (new MCP roots
support, sessionId-scoped daemon, screencast WebM/ffmpeg flag, etc.).

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
Pulls in updated dep versions from upstream (chrome-devtools-frontend
1.0.1625079, lighthouse 13.2.0, puppeteer 24.43.0, @paulirish/trace_engine
0.0.64) and drops tiktoken which upstream removed.

Co-Authored-By: Claude <noreply@anthropic.com>
Bumps the package, server, plugin, and runtime VERSION to 0.4.0 to
mark the upstream sync to chrome-devtools-mcp 0.24.0 (third-party
developer tools, agentic browsing in lighthouse, dialog-aware tool
rejection, env-var consistency fix, and dep bumps for
chrome-devtools-frontend, lighthouse, puppeteer, and trace_engine).

Co-Authored-By: Claude <noreply@anthropic.com>
@triuzzi

triuzzi commented May 7, 2026

Copy link
Copy Markdown
Author

Created against wrong repo, recreating on the fork.

@triuzzi triuzzi closed this May 7, 2026
@google-cla

google-cla Bot commented May 7, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@triuzzi triuzzi deleted the chore/sync-upstream-v0.24.0 branch May 7, 2026 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant