Skip to content

feat: support third-party developer tools#1982

Merged
wolfib merged 5 commits intomainfrom
rename-third-party-developer-tools
May 6, 2026
Merged

feat: support third-party developer tools#1982
wolfib merged 5 commits intomainfrom
rename-third-party-developer-tools

Conversation

@wolfib
Copy link
Copy Markdown
Contributor

@wolfib wolfib commented Apr 29, 2026

Enables "third-party developer tools" feature. This allows the inspected web page to expose tools which provide debugging information to Chrome DevTools for Agents.

Third-party developer tools enable web applications to expose internal state, component hierarchies, or specific debug data that cannot be deduced through static analysis. This allows Chrome DevTools for Agents to provide richer, more actionable context to AI agents during debugging sessions.

2 additional tools are enabled in Chrome DevTools for Agents for interacting with third-party developer tools: list_3p_developer_tools() and execute_3p_developer_tool.

Code changes in this PR:

  • Rename "in-page tools" to "third-party developer tools"
  • Unhide
  • Make available in CLI
  • Add documentation

Copy link
Copy Markdown
Collaborator

@OrKoN OrKoN left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This with conflict with #1962 Let's change the name once we are ready to unexperiment it?

@wolfib wolfib force-pushed the rename-third-party-developer-tools branch from f472551 to d426575 Compare May 6, 2026 12:12
@wolfib wolfib force-pushed the rename-third-party-developer-tools branch from 876f4d1 to 366d3dd Compare May 6, 2026 12:33
@OrKoN OrKoN changed the title chore: rename "in-page tools" to "third-party developer tools" feat: support third-party developer tools May 6, 2026
@OrKoN
Copy link
Copy Markdown
Collaborator

OrKoN commented May 6, 2026

Edited the title.

@OrKoN
Copy link
Copy Markdown
Collaborator

OrKoN commented May 6, 2026

Can you update the description with what the feature is about?

@wolfib wolfib added this pull request to the merge queue May 6, 2026
Merged via the queue into main with commit 7548c97 May 6, 2026
22 checks passed
@wolfib wolfib deleted the rename-third-party-developer-tools branch May 6, 2026 12:51
masamaru0513 pushed a commit to masamaru0513/chrome-devtools-mcp that referenced this pull request May 6, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.25.0](ChromeDevTools/chrome-devtools-mcp@chrome-devtools-mcp-v0.24.0...chrome-devtools-mcp-v0.25.0)
(2026-05-06)


### 🎉 Features

* support third-party developer tools
([ChromeDevTools#1982](ChromeDevTools#1982))
([7548c97](ChromeDevTools@7548c97))


### 🛠️ Fixes

* **input:** stop native select option clicks from timing out
([ChromeDevTools#1960](ChromeDevTools#1960))
([510ec0f](ChromeDevTools@510ec0f))
* make sure env variables are consistently applied when parsing args
([ChromeDevTools#1994](ChromeDevTools#1994))
([f45f068](ChromeDevTools@f45f068))


### 📄 Documentation

* extract WebMCP into its own category
([ChromeDevTools#1993](ChromeDevTools#1993))
([da0441d](ChromeDevTools@da0441d))
* remove token estimates
([ChromeDevTools#2003](ChromeDevTools#2003))
([14938ac](ChromeDevTools@14938ac))
* update generate-docs.ts tools output order
([ChromeDevTools#1991](ChromeDevTools#1991))
([895fc65](ChromeDevTools@895fc65)),
closes
[ChromeDevTools#1932](ChromeDevTools#1932)

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
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.

2 participants