feat: add experimental TOON support for structured content output#2042
Merged
Conversation
91642e4 to
3273670
Compare
2d2b4ba to
c36e1e2
Compare
c36e1e2 to
ea498ff
Compare
pull Bot
pushed a commit
to CrazyForks/chrome-devtools-mcp
that referenced
this pull request
Jun 8, 2026
🤖 I have created a release *beep* *boop* --- ## [1.2.0](ChromeDevTools/chrome-devtools-mcp@chrome-devtools-mcp-v1.1.1...chrome-devtools-mcp-v1.2.0) (2026-06-08) ### 🎉 Features * add experimental TOON support for structured content output ([ChromeDevTools#2042](ChromeDevTools#2042)) ([aa33bff](ChromeDevTools@aa33bff)) * Adds close_heapsnapshot MCP tool ([ChromeDevTools#2174](ChromeDevTools#2174)) ([8713b93](ChromeDevTools@8713b93)) * Handle multiple providers of third-party developer tools ([ChromeDevTools#2168](ChromeDevTools#2168)) ([30d59a7](ChromeDevTools@30d59a7)) * implement extension service worker logs ([ChromeDevTools#1915](ChromeDevTools#1915)) ([29e3898](ChromeDevTools@29e3898)) * memory debugging tools ([ChromeDevTools#2169](ChromeDevTools#2169)) ([0217397](ChromeDevTools@0217397)) * support allowedUrlPattern & blockedUrlPattern Options ([ChromeDevTools#2037](ChromeDevTools#2037)) ([02b4492](ChromeDevTools@02b4492)) ### 🛠️ Fixes * Cursor plugin homepage setting field ([ChromeDevTools#2173](ChromeDevTools#2173)) ([8971890](ChromeDevTools@8971890)) ### 📄 Documentation * **skill:** guide agent to prompt for --categoryExtensions ([ChromeDevTools#2189](ChromeDevTools#2189)) ([8b458f7](ChromeDevTools@8b458f7)) ### ⚡ Performance * lighthouse file saves to run concurrently ([ChromeDevTools#2178](ChromeDevTools#2178)) ([f90f863](ChromeDevTools@f90f863)) ### 🏗️ Refactor * change type of logger ([ChromeDevTools#2165](ChromeDevTools#2165)) ([bf0574d](ChromeDevTools@bf0574d)) * use validate files on the tool level ([ChromeDevTools#2152](ChromeDevTools#2152)) ([2e039c0](ChromeDevTools@2e039c0)), closes [ChromeDevTools#2150](ChromeDevTools#2150) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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
2 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.
Adds
--experimentalToonFormatboolean flag, controlling how structured content is formatted in text response.By default, custom shorthand format is used. With this flag, TOON format (see https://github.com/toon-format/toon) is used instead.
TOON format is supposed to be more token-efficient and less error-prone for agents to understand than json, but it's not clear if it will be better on those metrics than the custom format used so far. (Evals pending)
One clear benefit over custom format would be less code to maintain if we decide to fully switch to TOON, due to dropping custom formatters and reusing json formatters used for structuredContent anyways.