Add debugging member to ToolAnnotations - #253
Open
beaufortfrancois wants to merge 1 commit into
Open
beaufortfrancois wants to merge 1 commit into
beaufortfrancois wants to merge 1 commit into
Conversation
beaufortfrancois
force-pushed
the
debugging-member
branch
from
September 11, 2026 11:19
5c05290 to
c768a6b
Compare
Collaborator
Author
|
FYI I have a WIP Chromium CL at https://chromium-review.googlesource.com/c/chromium/src/+/8398587 |
markafoltz
self-requested a review
September 16, 2026 21:24
markafoltz
approved these changes
Sep 16, 2026
Collaborator
|
PR LGTM. One question that comes to mind is whether a tool marked as |
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
3 participants
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.
Following the WebML CG resolution, this PR adds a
debuggingboolean member to theToolAnnotationsdictionary to provide a way for web apps and frameworks to register tools intended specifically for developer tooling and inspection (e.g., Chrome DevTools AI assistance, testing frameworks) so that general-purpose/end-user agents can filter them out.Note that I went with
debuggingrather thandebuggingHintbecause it is a definitive categorization flag identifying the tool's intended domain/audience (developer/debugging tools vs. user-facing tools) rather than a behavioral hint about how the tool executes.Fixes #207
Preview | Diff