Conversation
This allows developers to mark specific tools as being intended for agents controlled by developers to debug the application. See: https://groups.google.com/a/chromium.org/g/chrome-ai-dev-preview/c/8tQWCpY6gVA/m/nNy_31okEgAJ.
UI forms are necessarily for end users and not fit for debugging use cases. There might be some developer-only panels which include signal forms where this annotation might be appropriate, but we're keeping it simple for now and can expand if/when such use cases arise. See: https://groups.google.com/a/chromium.org/g/chrome-ai-dev-preview/c/8tQWCpY6gVA/m/nNy_31okEgAJ
JeanMeche
approved these changes
Oct 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WebMCP introduced a new
debuggingannotation: https://groups.google.com/a/chromium.org/g/chrome-ai-dev-preview/c/8tQWCpY6gVA/m/nNy_31okEgAJThis PR exposes the option to
declareExperimentalWebMcpTool. It also hard-codesdebugging: falsefor signal forms tools under the assumption that all UI forms are intended for end users. That probably isn't 100% true, but I'd rather not expose this option until developers signal an interest in it.Existing Angular Chrome DevTools for Agents third party tools are unaffected and not in scope for using this annotation, as they are not implemented with WebMCP. We're talking with Chrome DevTools about potentially moving that direction, but this annotation is not sufficient as-is. The tools we have now require passing serializable references like DOM elements and JS objects which WebMCP does not currently support.