bumped chrome-devtools-mcp to v0.18.1

[Darshit42]

Summary

Bumps the pinned chrome-devtools-mcp version from 0.17.1 to 0.18.1 in the browser agent.

Details

changed the version in packages/core/src/agents/browser/browserManager.ts at line 29

Related Issues

Closes #20587

How to Validate

Pre-Merge Checklist

• Updated relevant documentation and README (if needed)
• Added/updated tests (if needed)
• Noted breaking changes (if any)
• Validated on required platforms/methods:
  • MacOS
    • npm run
    • npx
    • Docker
    • Podman
    • Seatbelt
  • Windows
    • npm run
    • npx
    • Docker
  • Linux
    • npm run
    • npx
    • Docker

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the pinned version of the chrome-devtools-mcp dependency within the browser agent to 0.18.1. This ensures the project utilizes the latest stable features and bug fixes from the Chrome DevTools Protocol client, enhancing compatibility and reliability for browser-related functionalities and addressing issue #20587.

Highlights

• Dependency Update: The chrome-devtools-mcp dependency has been updated from version 0.17.1 to 0.18.1.

Changelog

• packages/core/src/agents/browser/browserManager.ts
  • Updated the pinned version of chrome-devtools-mcp from 0.17.1 to 0.18.1.

Activity

• Pull request created by Darshit42.
• Validated on Windows using 'npm run' as per the pre-merge checklist.
• Marked as closing issue browser_agent - use chrome-devtools-mcp v0.18.1 #20587.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the pinned version of the chrome-devtools-mcp dependency from 0.17.1 to 0.18.1. The change is confined to the CHROME_DEVTOOLS_MCP_VERSION constant in packages/core/src/agents/browser/browserManager.ts. The update appears correct and isolated. Given the minor version increment, this is expected to be a safe update. No issues were found in this change.

_{Note: Security Review is unavailable for this PR.}

[lesteral]

@Darshit42 - thanks for working on this.

When I tried using CHROME_DEVTOOLS_MCP_VERSION = '0.18.1',
with a local build of the main branch as of early today,
I encountered an error related to the type_text tool being "duplicated."

I believe the explanation is as follows.

As of chrome-devtools-mcp release 0.18.0, a tool type_text was added.
(see ChromeDevTools/chrome-devtools-mcp#1026 - "feat: support type_text").

This new tool is identically named to a "custom tool" instantiated at https://github.com/google-gemini/gemini-cli/blob/main/packages/core/src/agents/browser/mcpToolWrapper.ts#L414:

  // Add custom composite tools
  tools.push(new TypeTextDeclarativeTool(browserManager, messageBus));

  debugLogger.log(
    `Total tools registered: ${tools.length} (${mcpTools.length} MCP + 1 custom)`,
  );

It seems to me that TypeTextDeclarativeTool may no longer be needed.

I found that I could successfully use (i.e., no "duplicate" tool error) chrome-devtools-mcp versions 0.18.1, 0.19.0, and 0.20.0 (released today), simply by commenting out the line:

tools.push(new TypeTextDeclarativeTool(browserManager, messageBus));

My testing included use of chrome-devtools-mcp's variant of type_text.

Some accommodation of this emergent type_text tool "duplication" will be needed in order to advance the CHROME_DEVTOOLS_MCP_VERSION.

(You might seek guidance from @gsquared94 regarding how to proceed.)

I hope this is helpful.

Regards,
Lester

[lesteral]

@Darshit42 - I just noticed that this issue is being addressed by #21177
As such, you might just close this PR.

Regards,
Lester