{"id":"prod_R6wKhmZIPwAQre41O_jpS","name":"Chrome","slug":"chrome","orgId":"org_ASekxqXI1HV68Hva5VhNC","url":"https://www.google.com/chrome/","description":"Cross-platform web browser; the largest-share browser by usage and the upstream for the Chromium project.","category":"developer-tools","kind":"platform","avatarUrl":null,"createdAt":"2026-05-07T10:48:26.014Z","embeddedAt":"2026-05-07T10:48:26.998Z","deletedAt":null,"sources":[{"id":"src_qlzIHRlAzo61CCxqeX3pq","slug":"chrome-developers-blog","name":"Chrome Developers Blog","type":"feed","url":"https://developer.chrome.com/blog/","metadata":"{\"feedUrl\":\"https://developer.chrome.com/feed.xml\",\"feedType\":\"rss\",\"feedLastModified\":\"Wed, 24 Jun 2026 07:17:56 GMT\",\"feedContentLength\":\"5688\",\"feedContentDepth\":\"summary-only\",\"enrichment\":{\"consecutiveFailures\":0}}","kind":"platform"},{"id":"src_uhOPXyseDAtQDEch5aQam","slug":"chrome-releases","name":"Chrome Releases","type":"feed","url":"https://chromereleases.googleblog.com/","metadata":"{\"feedUrl\":\"https://chromereleases.googleblog.com/feeds/posts/default\",\"feedType\":\"atom\",\"feedLastModified\":\"Wed, 24 Jun 2026 21:57:53 GMT\",\"feedContentLength\":\"0\"}","kind":"platform"}],"tags":["browser","web"],"aliases":[],"notice":null,"releases":[{"id":"rel_rAHC7UK0KtpeCILjVVT3b","version":null,"type":"feature","title":"Chrome Stable for iOS Update","summary":"Chrome Stable 150 (150.0.7871.51) for iOS includes stability and performance improvements.","titleGenerated":"Chrome Stable 150 for iOS ships with stability and performance improvements","titleShort":"Stability and performance improvements for iOS","content":"Hi everyone! We've just released Chrome Stable 150 (150.0.7871.51) for iOS; it'll become available on App Store in the next few hours.\n\nThis release includes stability and performance improvements. You can see a full list of the changes in the [Git log](https://chromium.googlesource.com/chromium/src/+log/150.0.7871.34..150.0.7871.51?pretty=fuller&n=10000). If you find a new issue, please let us know by [filing a bug](https://code.google.com/p/chromium/issues/entry?template=iOS%20Issue).\n\nChrome Release Team  \n[](https://www.google.com/chrome)[Google Chrome](https://www.google.com/chrome)","publishedAt":"2026-06-24T21:43:32.251Z","url":"http://chromereleases.googleblog.com/2026/06/chrome-stable-for-ios-update_0913956154.html","media":[],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":594,"contentTokens":164,"composition":{"bugs":0,"features":0,"enhancements":2}},{"id":"rel_X7WHQkj9LG8BdyaKO6Fon","version":null,"type":"feature","title":"Chrome for Android Update","summary":"Chrome 150 (150.0.7871.46) for Android is rolling out to a small percentage of users as an early Stable release, with stability and performance improvements.","titleGenerated":"Chrome for Android 150 early stable release","titleShort":"Chrome 150 early stable ships to Android","content":"Hello Everyone! We've just released Chrome 150 (150.0.7871.46) for Android to a small percentage of users. It'll become [available on Google Play](https://play.google.com/store/apps/details?id=com.android.chrome) over the next few days. You can find more details about early Stable releases [here](https://developer.chrome.com/blog/early-stable/).\n\nThis release includes stability and performance improvements. You can see a full list of the changes in the [Git log](https://chromium.googlesource.com/chromium/src/+log/149.0.7827.197..150.0.7871.46?pretty=fuller&n=10000). If you find a new issue, please let us know by [filing a bug](https://code.google.com/p/chromium/issues/entry?template=Android%20Issue).  \n  \nKrishna Govind  \n[Google Chrome](https://www.google.com/chrome/)","publishedAt":"2026-06-24T20:57:28.841Z","url":"http://chromereleases.googleblog.com/2026/06/chrome-for-android-update_01850164664.html","media":[],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":779,"contentTokens":203,"composition":null},{"id":"rel_hVwCY9OhG_EGZPsVEhXK6","version":null,"type":"feature","title":"Early Stable Update for Desktop","summary":"The Stable channel has been updated to 150.0.7871.46/.47 for Windows and Mac as part of our early stable release to a small percentage of users. A ful...","titleGenerated":null,"titleShort":null,"content":"The Stable channel has been updated to 150.0.7871.46/.47 for Windows and Mac as part of our early stable release to a small percentage of users. A full list of changes in this build is available in the [log](https://chromium.googlesource.com/chromium/src/+log/149.0.7827.197..150.0.7871.47?pretty=fuller&n=10000).\n\nYou can find more details about early Stable releases [here](https://developer.chrome.com/blog/early-stable/).\n\nInterested in switching release channels?  Find out how [here](https://www.chromium.org/getting-involved/dev-channel). If you find a new issue, please let us know by [filing a bug](https://crbug.com/). The [community help forum](https://support.google.com/chrome/community) is also a great place to reach out for help or learn about common issues.\n\n  \n\nDaniel Yip\n\nGoogle Chrome","publishedAt":"2026-06-24T19:05:57.103Z","url":"http://chromereleases.googleblog.com/2026/06/early-stable-update-for-desktop_01696591429.html","media":[],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":805,"contentTokens":207,"composition":null},{"id":"rel_1vn_iclL1Hd9bpihe_qQ3","version":null,"type":"feature","title":"Chrome Beta for iOS Update","summary":"Hi everyone! We've just released Chrome Beta 150 (150.0.7871.52) for iOS; it'll become available on App Store in the next few days.\n\nYou can see a par...","titleGenerated":"Chrome Beta for iOS 150.0.7871.52 released","titleShort":null,"content":"Hi everyone! We've just released Chrome Beta 150 (150.0.7871.52) for iOS; it'll become available on App Store in the next few days.\n\nYou can see a partial list of the changes in the [Git log](https://chromium.googlesource.com/chromium/src/+log/150.0.7871.35..150.0.7871.52?pretty=fuller&n=10000). If you find a new issue, please let us know by [filing a bug](https://code.google.com/p/chromium/issues/entry?template=iOS%20Issue).\n\nChrome Release Team  \n[](https://www.google.com/chrome)[Google Chrome](https://www.google.com/chrome)","publishedAt":"2026-06-24T18:58:32.892Z","url":"http://chromereleases.googleblog.com/2026/06/chrome-beta-for-ios-update_01307594816.html","media":[],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":532,"contentTokens":156,"composition":null},{"id":"rel_R9B4KaE1ZnJ0Zb7XIvJkj","version":null,"type":"feature","title":"Chrome Beta for Desktop Update","summary":"Chrome Beta for Windows, Mac, and Linux updated to version 150.0.7871.46.","titleGenerated":"Chrome Beta for Desktop update to 150.0.7871.46","titleShort":"Beta channel bumps to 150.0.7871.46","content":"The Beta channel has been updated to 150.0.7871.46 for Windows, Mac and Linux.\n\nA partial list of changes is available in the [Git log](https://chromium.googlesource.com/chromium/src/+log/150.0.7871.24..150.0.7871.46?pretty=fuller&n=10000). Interested in [switching](https://www.chromium.org/getting-involved/dev-channel/) release channels? Find out [how](https://www.chromium.org/getting-involved/dev-channel/). If you find a new issue, please let us know by [filing a bug](https://crbug.com/). The [community help forum](https://productforums.google.com/forum/#!forum/chrome) is also a great place to reach out for help or learn about common issues.\n\nChrome Release Team  \n[](https://www.google.com/chrome)[Google Chrome](https://www.google.com/chrome)","publishedAt":"2026-06-24T17:13:32.649Z","url":"http://chromereleases.googleblog.com/2026/06/chrome-beta-for-desktop-update_02072900116.html","media":[],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":754,"contentTokens":204,"composition":null},{"id":"rel_zn4htoMWo04ZsgDVcpb0b","version":null,"type":"feature","title":"Chrome Beta for Android Update","summary":"Chrome Beta for Android updated to version 150.0.7871.46.","titleGenerated":"Chrome Beta for Android updated to version 150.0.7871.46","titleShort":"Chrome Beta 150.0.7871.46 for Android","content":"Hi everyone! We've just released Chrome Beta 150 (150.0.7871.46) for Android. It's now available on [Google Play](https://play.google.com/store/apps/details?id=com.chrome.beta).\n\nYou can see a partial list of the changes in the [Git log](https://chromium.googlesource.com/chromium/src/+log/150.0.7871.28..150.0.7871.46?pretty=fuller&n=10000). For details on new features, check out the [Chromium blog](https://blog.chromium.org), and for details on web platform updates, check [here](https://www.chromestatus.com/features#milestone%3D150).\n\nIf you find a new issue, please let us know by [filing a bug](https://code.google.com/p/chromium/issues/entry?template=Android%20Issue).\n\nChrome Release Team  \n[](https://www.google.com/chrome)[Google Chrome](https://www.google.com/chrome)","publishedAt":"2026-06-24T13:13:32.305Z","url":"http://chromereleases.googleblog.com/2026/06/chrome-beta-for-android-update_0811957371.html","media":[],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":780,"contentTokens":214,"composition":null},{"id":"rel_EwwZTff9FFHuhQjMXJQPi","version":null,"type":"feature","title":"Chrome for Android Update","summary":"Hi, everyone! We've just released **Chrome 149 (149.0.7827.197)** for Android. It'll become [available on Google Play](https://play.google.com/store/a...","titleGenerated":"Chrome for Android 149.0.7827.197 stability update","titleShort":null,"content":"Hi, everyone! We've just released **Chrome 149 (149.0.7827.197)** for Android. It'll become [available on Google Play](https://play.google.com/store/apps/details?id=com.android.chrome) over the next few days. \n\nThis release includes stability and performance improvements. You can see a full list of the changes in the [Git log](https://chromium.googlesource.com/chromium/src/+log/149.0.7827.159..149.0.7827.197?pretty=fuller&n=10000). If you find a new issue, please let us know by [filing a bug](https://code.google.com/p/chromium/issues/entry?template=Android%20Issue).\n\n  \n\nAndroid releases contain the same security fixes as their corresponding [Desktop releases](https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0482630350.html) (Windows & Mac: 149.0.7827.155/156, Linux: 149.0.7872.155) unless otherwise noted.\n\n  \n\nHarry Souders\n\n[Google Chrome](https://www.google.com/chrome/)","publishedAt":"2026-06-23T23:00:00.114Z","url":"http://chromereleases.googleblog.com/2026/06/chrome-for-android-update_01705291676.html","media":[],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":916,"contentTokens":249,"composition":null},{"id":"rel_mvOYxQ31v1ei9EeCP1aMz","version":null,"type":"feature","title":"Extended Stable Update for Desktop","summary":"The Extended Stable channel has been updated to 148.0.7778.280 for Windows and Mac which will roll out over the coming days/weeks.\n\n  \n\nA full list of...","titleGenerated":"Chrome Extended Stable 148.0.7778.280 for Windows and Mac","titleShort":null,"content":"The Extended Stable channel has been updated to 148.0.7778.280 for Windows and Mac which will roll out over the coming days/weeks.\n\n  \n\nA full list of changes in this build is available in the [log](https://chromium.googlesource.com/chromium/src/+log/148.0.7778.271..148.0.7778.280?pretty=fuller&n=10000). Interested in switching release channels? Find out how [here](https://www.chromium.org/getting-involved/dev-channel). If you find a new issue, please let us know by [filing a bug](https://crbug.com/). The [community help forum](https://productforums.google.com/forum/#!forum/chrome) is also a great place to reach out for help or learn about common issues.\n\nDaniel Yip\n\nGoogle Chrome","publishedAt":"2026-06-23T18:59:57.405Z","url":"http://chromereleases.googleblog.com/2026/06/extended-stable-update-for-desktop_0779765963.html","media":[],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":689,"contentTokens":182,"composition":null},{"id":"rel_Urz_OAz87KCqjOfllTJX8","version":null,"type":"feature","title":"Stable Channel Update for Desktop","summary":"The Stable channel has been updated to 149.0.7827.196/197 for Windows and Mac and 149.0.7827.196 for Linux, which will roll out over the coming days/w...","titleGenerated":"Chrome 149.0.7827.196 Stable channel update","titleShort":null,"content":"The Stable channel has been updated to 149.0.7827.196/197 for Windows and Mac and 149.0.7827.196 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available in the [Log](https://chromium.googlesource.com/chromium/src/+log/149.0.7827.157..149.0.7827.197?pretty=fuller&n=10000)\n\n  \n\nInterested in switching release channels? Find out how [here](https://www.chromium.org/getting-involved/dev-channel). If you find a new issue, please let us know by [filing a bug](https://crbug.com/). The [community help forum](https://support.google.com/chrome/community) is also a great place to reach out for help or learn about common issues.\n\n  \n\nDaniel Yip\n\nGoogle Chrome","publishedAt":"2026-06-23T18:37:55.829Z","url":"http://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0482630350.html","media":[],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":707,"contentTokens":193,"composition":null},{"id":"rel_jUl_VN1op1R35CyZXwHL0","version":null,"type":"feature","title":"Beta Channel Update for ChromeOS / ChromeOS Flex","summary":"ChromeOS Beta channel updated to browser version 150.0.7871.40 and OS version 16700.25.0 for most ChromeOS devices.","titleGenerated":"ChromeOS Beta channel moves to 150.0.7871.40 (OS 16700.25.0)","titleShort":"ChromeOS Beta reaches version 150","content":"The Beta channel is being updated to OS version 16700.25.0 (Browser version 150.0.7871.40) for most ChromeOS devices.\n\nIf you find new issues, please let us know one of the following ways:\n\n  \n\n1. [File a bug](https://bugs.chromium.org/p/chromium/issues/list)\n    \n2. Visit our ChromeOS communities\n    \n\n1. General: [Chromebook Help Community](https://support.google.com/chromebook/community/?hl=en&gpf=%23!forum%2Fchromebook-central)\n    \n2. Beta Specific: [ChromeOS Beta Help Community](https://support.google.com/chromeos-beta/community)\n    \n\n4. [Report an issue or send feedback on Chrome](https://support.google.com/chrome/answer/95315?hl=en&co=GENIE.Platform%3DDesktop)\n    \n5. Interested in switching channels? [Find out how.](https://support.google.com/chromebook/answer/1086915)\n    \n\n  \n\nAlon Bajayo\n\nGoogle ChromeOS\n\n ![Share on Twitter](https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png)![Share on Facebook](https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png)","publishedAt":"2026-06-23T18:28:37.217Z","url":"http://chromereleases.googleblog.com/2026/06/beta-channel-update-for-chromeos_01991392350.html","media":[{"type":"image","url":"https://www.gstatic.com/images/icons/material/system/2x/post_twitter_black_24dp.png"},{"type":"image","url":"https://www.gstatic.com/images/icons/material/system/2x/post_facebook_black_24dp.png"}],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":1041,"contentTokens":270,"composition":null},{"id":"rel_5mkNlJdhclodALxo2ecX2","version":null,"type":"feature","title":"A developer toolkit to make your website agent-ready","summary":"Lighthouse adds an Agentic browsing category (M150+) with deterministic audits for accessibility, stability, and WebMCP integration. Chrome DevTools for Agents provides a testing persona to simulate agent interaction, invoke Lighthouse audits, and debug machine-readable signals.","titleGenerated":"Chrome launches Lighthouse agentic browsing audits and DevTools for agents","titleShort":"Lighthouse agentic browsing audits; DevTools for agents","content":"# A developer toolkit to make your website agent-ready\n\nAs AI agents evolve from only generating text to browsing, interacting, and completing complex tasks on your website, developers need dedicated tools to ensure a high-quality experience for these non-human users. The new Lighthouse Agentic browsing category, coupled with enhancements to Chrome DevTools, provides deterministic audits and a testing framework to help you build agent-ready websites.\n\nThe shift to the agentic web involves two major stages: agents *searching* the web and agents *using* the web.\n\nWhen agents are just searching for websites, the [principles for Search Engine Optimization (SEO) still apply](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide). In this blog post, we focus on the work that developers can do when an agent interacts directly with the website.\n\n## Audit, improve, and debug your agent-ready website\n\nFor an AI agent to reliably complete a flow on your site, such as booking an appointment or placing an order, it needs predictable, machine-readable signals. Here are the tools to help you assess and improve that readiness.\n\n### Audit your website agentic-readiness\n\nThe new [Agentic browsing category](/docs/lighthouse/agentic-browsing/scoring) in Lighthouse is available starting from M150 and provides developers with a set of deterministic audits to assess how agent-friendly their websites are, encouraging the adoption of new industry standards.\n\n- **What the audits check**: The audits focus on three key areas critical for machine interaction:\n    \n    -   **Accessibility**: Accessibility is for humans first. Agents rely on the [accessibility tree](https://web.dev/learn/accessibility/aria-html#the_accessibility_tree), derived from DOM for assistive technology (AT), as their primary data model. The Agentic Browsing audit verifies a subset of categories from the [Accessibility audit](/docs/lighthouse/accessibility/scoring) that are critical for machine interaction. For example, both audits verify that every interactive element has a programmatic name. A well-formed accessibility tree is the primary way AI agents understand your page.\n    -   **Stability**: Measures visual stability using Cumulative Layout Shift (CLS) to ensure elements don't move unexpectedly, preventing agent misclicks.\n    -   **WebMCP integration**: Checks for the availability of registered WebMCP tools, forms missing declarative WebMCP, and schema validity. Adopting WebMCP helps agents explicitly expose your site's logic and forms, making interaction reliable.\n- **The score**: Unlike other Lighthouse categories, at the time of publication, Agentic Browsing is *informational and unbenchmarked*. The focus is on providing actionable signals (pass or fail status and warnings) rather than a definitive ranking.\n    \n\nTo learn more about the specific audit checks and what you can do to improve, see the documentation for [Agent browsing audits for Lighthouse](/docs/lighthouse/agentic-browsing).\n\n### Make interactions between agent and website faster and more reliable\n\nWebMCP is a proposed standard that aims to expose structure tools to AI Agents on existing websites, accelerating and simplifying agent interactions. For more information about implementation, see [Read about WebMCP](/blog/webmcp-epp).\n\n### Implement latest features using your preferred coding agent\n\nModern Web Guidance provides a collection of best practices and skills to help developers build agent-ready websites. It includes the `webmcp` skill, which lets you delegate implementation of the WebMCP tools to your coding agent. By integrating Modern Web Guidance into your development workflow, you can ensure your application is built with modern, agent-friendly standards from the ground up. To learn more, see [Modern Web Guidance documentation](http://goo.gle/modern-web-guidance).\n\n### Test and debug your website with Chrome DevTools for agents\n\nFor deep debugging and iterative development, [Chrome DevTools for Agents](/docs/devtools/agents) offers a unique testing persona. It lets you transform your own AI-assisted IDE or coding agent into a browsing agent, giving you a high degree of control.\n\nWith DevTools for agents you can:\n\n- **Simulate agent interaction:** You can simulate the precise steps an agent would take, effectively \"becoming the user\" (or the agent) to reproduce failures and verify that your website's flows are deterministic.\n- **Direct Lighthouse invocation:** Your testing environment can directly invoke the `lighthouse_audit` tool on the active tab. This provides an instant, multi-category health check based on the page's current state, allowing you to verify fixes iteratively against the Agentic Browsing standards.\n- **Screencast and debug:** The tool offers detailed logging and screencast capabilities, so you can see exactly how the agent perceives and interacts with the page. This exposes some machine-readable signals, such as the accessibility tree, that may confuse the agent.\n\nThis helps you ensure a high-quality experience for non-human users before deployment.\n\nTo learn more about capabilities and configuration of Chrome DevTools for Agents, see our [GitHub repository](https://github.com/ChromeDevTools/chrome-devtools-mcp#chrome-devtools-for-agents).\n\n**Note:** Make sure that in `chrome://inspect` Remote Debugging is enabled. If you want to trigger WebMCP tools from Chrome DevTools for Agents, make sure your browser, for example Chrome Canary, is running and has enabled the [Chrome flag](/docs/web-platform/chrome-flags) needed for WebMCP: `chrome://flags/#enable-webmcp-testing`.\n\nThe following example configuration of Chrome DevTools for Agents (`~/.gemini/config/mcp_config.json` for AntigravityCLI or configured in Antigravity) connects to Chrome Canary.\n\n```\n{\n  \"mcpServers\": {\n    \"chrome-devtools\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"chrome-devtools-mcp@latest\",\n        \"--autoConnect\",\n        \"--categoryExperimentalWebmcp\",\n        \"--channel=canary\"\n      ]\n    }\n  }\n}\n```\n\n**Tip:** Experimental features of Chrome DevTools for Agents like `--categoryExperimentalWebmcp` or `--experimentalScreencast` can behave in an unstable way. If you are using AntigravityCLI and notice unexpected behavior, restart the tool.\n\nUse the example query: *\"Using Chrome DevTools MCP, go to https://googlechromelabs.github.io/webmcp-tools/demos/pizza-maker/ and create me a pizza with 10 mushrooms and 2 bell peppers; make sure to give me a summary of what you did and what tools you called.\"*\n\n![](/static/blog/agent-ready-toolkit/img/agentic-browsing-pizza.png \"Chrome DevTools for Agents executing pizza maker demo\")\n\nYou can also use DevTools for Agents to perform agentic-readiness Lighthouse audit:\n\n\"*I want to do an agentic lighthouse audit on https://googlechromelabs.github.io/webmcp-tools/demos/french-bistro/?notoolname using Chrome DevTools MCP; give me a full summary.*\"\n\n![](/static/blog/agent-ready-toolkit/img/agentic-browsing-LH-audit.png \"Lighthouse audit in Chrome DevTools for Agents\")\n\n## What's next\n\nTo contribute and join the discussion, see [the official Lighthouse repository](https://github.com/GoogleChrome/lighthouse).\n\nFor more information about WebMCP, see [WebMCP documentation](/docs/ai/webmcp). For more information about Modern Web Guidance, see [Modern Web Guidance documentation](http://goo.gle/modern-web-guidance). For more information about optimizing your website for generative AI, see [Optimizing your website for generative AI features on Google Search](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide).","publishedAt":"2026-06-22T07:00:00.000Z","url":"https://developer.chrome.com/blog/agent-ready-toolkit?hl=en","media":[],"prerelease":false,"source":{"slug":"chrome-developers-blog","name":"Chrome Developers Blog","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":7665,"contentTokens":1610,"composition":{"bugs":0,"features":2,"enhancements":0}},{"id":"rel_l1I1J-Mf2cX_EMWT6xh4q","version":null,"type":"feature","title":"Beta Channel Update for ChromeOS / ChromeOS Flex","summary":"The Beta channel is being updated to OS version 16700.20.0 (Browser version 150.0.7871.32) for most ChromeOS devices.\n\nIf you find new issues, please ...","titleGenerated":"Chrome OS 16700.20.0 beta channel update","titleShort":null,"content":"The Beta channel is being updated to OS version 16700.20.0 (Browser version 150.0.7871.32) for most ChromeOS devices.\n\nIf you find new issues, please let us know one of the following ways:\n\n  \n\n1. [File a bug](https://bugs.chromium.org/p/chromium/issues/list)\n    \n2. Visit our ChromeOS communities\n    \n\n1. General: [Chromebook Help Community](https://support.google.com/chromebook/community/?hl=en&gpf=%23!forum%2Fchromebook-central)\n    \n2. Beta Specific: [ChromeOS Beta Help Community](https://support.google.com/chromeos-beta/community)\n    \n\n4. [Report an issue or send feedback on Chrome](https://support.google.com/chrome/answer/95315?hl=en&co=GENIE.Platform%3DDesktop)\n    \n5. Interested in switching channels? [Find out how.](https://support.google.com/chromebook/answer/1086915)\n    \n\n  \n\nAlon Bajayo\n\nGoogle ChromeOS","publishedAt":"2026-06-18T18:21:43.705Z","url":"http://chromereleases.googleblog.com/2026/06/beta-channel-update-for-chromeos_0409608557.html","media":[],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":828,"contentTokens":219,"composition":null},{"id":"rel_9WneJMWCkmDAlJ-Qt4nEz","version":null,"type":"feature","title":"Chrome Dev for Android Update","summary":"Hi everyone! We've just released Chrome Dev 151 (151.0.7896.3) for Android. It's now available on [Google Play](https://play.google.com/store/apps/det...","titleGenerated":"Chrome Dev for Android 151.0.7896.3 update","titleShort":null,"content":"Hi everyone! We've just released Chrome Dev 151 (151.0.7896.3) for Android. It's now available on [Google Play](https://play.google.com/store/apps/details?id=com.chrome.dev).\n\nYou can see a partial list of the changes in the [Git log](https://chromium.googlesource.com/chromium/src/+log/151.0.7885.0..151.0.7896.3?pretty=fuller&n=10000). For details on new features, check out the [Chromium blog](https://blog.chromium.org), and for details on web platform updates, check [here](https://www.chromestatus.com/features#milestone%3D151).\n\nIf you find a new issue, please let us know by [filing a bug](https://code.google.com/p/chromium/issues/entry?template=Android%20Issue).\n\nChrome Release Team  \n[](https://www.google.com/chrome)[Google Chrome](https://www.google.com/chrome)","publishedAt":"2026-06-18T17:28:32.466Z","url":"http://chromereleases.googleblog.com/2026/06/chrome-dev-for-android-update_01200124948.html","media":[],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":775,"contentTokens":214,"composition":null},{"id":"rel_vzVt9-VZW6Oomy2BW9t-J","version":null,"type":"feature","title":"Chrome Dev for Desktop Update","summary":"The Dev channel has been updated to version 151.0.7896.2 for Windows, Mac, and Linux with changes in the Git log.","titleGenerated":"Chrome Dev for Desktop 151.0.7896.2 released","titleShort":"Dev channel update","content":"The Dev channel has been updated to 151.0.7896.2 for Windows, Mac and Linux.\n\nA partial list of changes is available in the [Git log](https://chromium.googlesource.com/chromium/src/+log/151.0.7886.2..151.0.7896.2?pretty=fuller&n=10000). Interested in [switching](https://www.chromium.org/getting-involved/dev-channel/) release channels? Find out [how](https://www.chromium.org/getting-involved/dev-channel/). If you find a new issue, please let us know by [filing a bug](https://crbug.com/). The [community help forum](https://productforums.google.com/forum/#!forum/chrome) is also a great place to reach out for help or learn about common issues.\n\nChrome Release Team  \n[](https://www.google.com/chrome)[Google Chrome](https://www.google.com/chrome)","publishedAt":"2026-06-18T14:13:33.274Z","url":"http://chromereleases.googleblog.com/2026/06/chrome-dev-for-desktop-update_01724281417.html","media":[],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":750,"contentTokens":204,"composition":null},{"id":"rel_jxA8TDaXkNjMSDHX6o0XN","version":null,"type":"feature","title":"Unlock runtime insights: Introducing third-party developer tools for Chrome DevTools for agents","summary":"Chrome DevTools for agents v0.25.0 introduces a Discovery API that lets frameworks expose runtime tools to AI agents via an event-based JavaScript API and MCP integration. Angular provides Signal Graph and DI Graph tools; React is experimenting.","titleGenerated":"Chrome DevTools for agents v0.25.0 lets frameworks expose runtime tools via a discovery API","titleShort":"Third-party developer tools API for agentic debugging","content":"# Unlock runtime insights: Introducing third-party developer tools for Chrome DevTools for agents\n\nTo debug a modern web application effectively, an AI agent needs more than just your source code; it needs to understand how the application behaves at runtime.\n\nWe are excited to [introduce third-party developer tools](/docs/devtools/agents/use-cases/third-party-tools) for [Chrome DevTools for agents](/docs/devtools/agents). Now, your apps and frameworks can give AI agents a direct look at their internal state. This helps agents connect the dots between what's happening on the screen and the logic running behind the scenes.\n\n## The goal: Beyond static analysis\n\nModern web development is built on abstractions—frameworks like Angular, React, or Vue; CMS platforms like WordPress or Shopify; and libraries for CSS, 3D graphics, or animations. While DevTools has direct access to the final rendered DOM, the \"truth\" of an application often lives inside the framework's internal state: component hierarchies, JavaScript signals, or backend state.\n\nOur goal with third-party developer tools is to provide a path for any library to share this rich, actionable context with AI agents. By doing so, this lets agents debug issues that were previously \"invisible\" to them, for example:\n\n- **Component hierarchies:** Map a DOM element on the page directly to its corresponding framework component and internal state.\n- **Internal state inspection:** Access server-side state or database content directly within the debugging session.\n\n## How it works: The Discovery API\n\nThird-party developer tools use an event-based JavaScript API. The Chrome DevTools MCP server discovers these tools by dispatching a `devtoolstooldiscovery` event on the global `window` object. The `devtoolstooldiscovery` event is automatically dispatched on every page navigation, or if the selected page is changed, and can be dispatched explicitly using the `list_3p_developer_tools` MCP tool.\n\n### Implement your own tools\n\nTo expose tools from your library or application, you need to listen for this discovery event and respond with a `ToolGroup`.\n\n```\nwindow.addEventListener('devtoolstooldiscovery', (event) => {\n  event.respondWith({\n    name: \"My Library Tools\",\n    description: \"Tools for inspecting internal library state\",\n    tools: [\n      {\n        name: \"getInternalState\",\n        description: \"Returns the current internal state of the framework.\",\n        inputSchema: {\n          type: \"object\",\n          properties: {\n            componentId: { type: \"string\" }\n          }\n        },\n        execute: async (input) => {\n          // Access your framework's internal registry\n          return myFramework.getState(input.componentId);\n        }\n      }\n    ]\n  });\n});\n```\n\nImplementation is as follows:\n\n1. **Define the schema:** Use [JSON Schema](https://json-schema.org/) to define the input your tool expects.\n2. **Handle the logic:** Implement an `execute` function that runs in the page's context and returns serializable data.\n3. **DOM elements:** Non-serializable objects cannot be sent between the page and DevTools for agents. DOM elements are an exception. When your tools return DOM elements, DevTools for agents automatically maps them to the same UIDs used by the [`take_snapshot`](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/tool-reference.md#take_snapshot) tool. This lets your agent interact with all page elements (whether they come from a framework or from a page snapshot) in the same way.\n\n## Interact with tools using MCP\n\nOnce you register your tools, your coding agent can interact with them through DevTools for agents. The `list_3p_developer_tools` MCP tool returns descriptions of the third-party tools available on the page. Additionally, when the selected page changes (for example, after navigation), DevTools appends a list of available tools to the MCP tool response.\n\nTo use these tools, your agent calls `execute_3p_developer_tool`. DevTools automatically validates input parameters to ensure they match the tool's definition.\n\nYou can also invoke tools using the `evaluate_script` MCP tool. Your agent provides a JavaScript snippet that DevTools executes on the page. This snippet can call third-party developer tools and immediately use their output for further calculations.\n\nUsing `evaluate_script` is effective for complex debugging because it lets agents:\n\n- **Compose operations**: Combine multiple steps into a single execution.\n- **Handle non-serializable values**: Process framework-specific objects or signals directly in the page context.\n- **Optimize performance**: Minimize serialization overhead and avoid multiple round trips between the agent and the browser.\n\n## Early success: Angular integration\n\nWe've been collaborating with the Angular team, who implemented two third-party developer tools:\n\n1. **Signal Graph tool:** Gives agents the ability to visualize relationships between the state and the view, helping them identify dependencies that cause infinite loops or failed updates.\n2. **Dependency Injection (DI) Graph tool:** Exposes the element injectors, which lets agents see exactly where a service is provided or where it is missing. Because Angular's DI graph is a runtime-only construct, static analysis alone cannot debug provider errors.\n\nA screencast showing an AI agent using the Angular Signal Graph tool to debug a reactive loop.\n\nThe React team has also started [experimenting](https://github.com/react/react/pull/36600) with third-party developer tools.\n\n## Build the future of agentic debugging with us\n\nThis experimental feature is available in Chrome DevTools for agents starting with version 0.25.0. To enable it, use the `--categoryExperimentalThirdParty` command-line flag.\n\nIf you maintain a framework, library, or tool and want to improve the debugging experience for coding agents, we'd love to collaborate:\n\n- **Explore the docs:** [Technical Guide on GitHub](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/third-party-developer-tools.md).\n- **Reach out:** We are looking for partners to iterate on these APIs and help define the future of AI-powered web debugging. You can [create an issue in the GitHub repository](https://github.com/ChromeDevTools/chrome-devtools-mcp/issues) to reach out.\n\nJoin us in building the future of agentic web development together!","publishedAt":"2026-06-18T07:00:00.000Z","url":"https://developer.chrome.com/blog/devtools-for-agents-3p-tools?hl=en","media":[],"prerelease":false,"source":{"slug":"chrome-developers-blog","name":"Chrome Developers Blog","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":6381,"contentTokens":1302,"composition":{"bugs":0,"features":1,"enhancements":0}},{"id":"rel_CajHAEXSqCz3H-JNFJsQX","version":null,"type":"feature","title":"Chrome Stable for iOS Update","summary":"Chrome Stable 150 (150.0.7871.34) for iOS includes stability and performance improvements.","titleGenerated":"Chrome 150 for iOS ships with stability and performance improvements","titleShort":"Stability and performance improvements on iOS","content":"Hi everyone! We've just released Chrome Stable 150 (150.0.7871.34) for iOS; it'll become available on App Store in the next few hours.\n\nThis release includes stability and performance improvements. You can see a full list of the changes in the [Git log](https://chromium.googlesource.com/chromium/src/+log/149.0.7827.137..150.0.7871.34?pretty=fuller&n=10000). If you find a new issue, please let us know by [filing a bug](https://code.google.com/p/chromium/issues/entry?template=iOS%20Issue).\n\nChrome Release Team  \n[](https://www.google.com/chrome)[Google Chrome](https://www.google.com/chrome)","publishedAt":"2026-06-17T21:13:32.471Z","url":"http://chromereleases.googleblog.com/2026/06/chrome-stable-for-ios-update_0343727604.html","media":[],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":595,"contentTokens":164,"composition":null},{"id":"rel_3Mwhg1GlQAD913ZOZWraN","version":null,"type":"feature","title":"Chrome for Android Update","summary":"Chrome 150 (150.0.7871.28) for Android is rolling out to a small percentage of users, with a full rollout to Google Play over the coming days. Includes stability and performance improvements.","titleGenerated":"Chrome 150 for Android rolls out with stability and performance improvements","titleShort":"Stability and performance improvements in Chrome 150 for Android","content":"Hello Everyone! We've just released Chrome 150 (150.0.7871.28) for Android to a small percentage of users. It'll become [available on Google Play](https://play.google.com/store/apps/details?id=com.android.chrome) over the next few days. You can find more details about early Stable releases [here](https://developer.chrome.com/blog/early-stable/).\n\nThis release includes stability and performance improvements. You can see a full list of the changes in the [Git log](https://chromium.googlesource.com/chromium/src/+log/149.0.7827.159..150.0.7871.28?pretty=fuller&n=10000). If you find a new issue, please let us know by [filing a bug](https://code.google.com/p/chromium/issues/entry?template=Android%20Issue).  \n  \nHarry Souders  \n[Google Chrome](https://www.google.com/chrome/)","publishedAt":"2026-06-17T21:00:00.166Z","url":"http://chromereleases.googleblog.com/2026/06/chrome-for-android-update_0779506642.html","media":[],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":778,"contentTokens":202,"composition":{"bugs":0,"features":0,"enhancements":2}},{"id":"rel_qNBkaMLrfxcxtuH0oeF8j","version":null,"type":"feature","title":"Stable Channel Update for ChromeOS / ChromeOS Flex","summary":"The ChromeOS Stable channel is being updated to OS version 16667.47.0 (Browser version 149.0.7827.153) for most ChromeOS devices.\n\nIf you find new iss...","titleGenerated":"ChromeOS Stable Channel update to OS version 16667.47.0","titleShort":null,"content":"The ChromeOS Stable channel is being updated to OS version 16667.47.0 (Browser version 149.0.7827.153) for most ChromeOS devices.\n\nIf you find new issues, please let us know one of the following ways:\n\n1. [File a bug](https://bugs.chromium.org/p/chromium/issues/list)\n2. Visit our ChromeOS communities\n    \n\n1. General: [Chromebook Help Community](https://support.google.com/chromebook/community/?hl=en&gpf=%23!forum%2Fchromebook-central)\n    \n2. Beta Specific: [ChromeOS Beta Help Community](https://support.google.com/chromeos-beta/community)\n    \n\n4. [Report an issue or send feedback on Chrome](https://support.google.com/chrome/answer/95315?hl=en&co=GENIE.Platform%3DDesktop)\n    \n5. Interested in switching channels? [Find out how.](https://support.google.com/chromebook/answer/1086915)\n    \n\nLuis Menezes\n\nGoogle ChromeOS","publishedAt":"2026-06-17T20:48:04.973Z","url":"http://chromereleases.googleblog.com/2026/06/stable-channel-update-for-chromeos_01459451963.html","media":[],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":828,"contentTokens":218,"composition":null},{"id":"rel_eiQquXbW9umg94NAPpFa0","version":null,"type":"feature","title":"Chrome Beta for iOS Update","summary":"Chrome Beta 150 (150.0.7871.35) for iOS has been released and will appear on the App Store in the coming days. The release notes reference a Git log for the change list between versions 150.0.7871.14 and 150.0.7871.35.","titleGenerated":"Chrome Beta for iOS 150.0.7871.35 released","titleShort":"Chrome Beta 150 ships for iOS","content":"Hi everyone! We've just released Chrome Beta 150 (150.0.7871.35) for iOS; it'll become available on App Store in the next few days.\n\nYou can see a partial list of the changes in the [Git log](https://chromium.googlesource.com/chromium/src/+log/150.0.7871.14..150.0.7871.35?pretty=fuller&n=10000). If you find a new issue, please let us know by [filing a bug](https://code.google.com/p/chromium/issues/entry?template=iOS%20Issue).\n\nChrome Release Team  \n[](https://www.google.com/chrome)[Google Chrome](https://www.google.com/chrome)","publishedAt":"2026-06-17T17:43:32.884Z","url":"http://chromereleases.googleblog.com/2026/06/chrome-beta-for-ios-update_01693329942.html","media":[],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":532,"contentTokens":156,"composition":null},{"id":"rel_uiDDxJRiHQvsNL4VBcPU9","version":null,"type":"feature","title":"Early Stable Update for Desktop","summary":"The Stable channel has been updated to 150.0.7871.24/.25 for Windows and Mac as part of our early stable release to a small percentage of users. A ful...","titleGenerated":"Chrome 150.0.7871.24 early stable release for desktop","titleShort":null,"content":"The Stable channel has been updated to 150.0.7871.24/.25 for Windows and Mac as part of our early stable release to a small percentage of users. A full list of changes in this build is available in the [log](https://chromium.googlesource.com/chromium/src/+log/149.0.7827.156..150.0.7871.25?pretty=fuller&n=10000).\n\nYou can find more details about early Stable releases [here](https://developer.chrome.com/blog/early-stable/).\n\nInterested in switching release channels?  Find out how [here](https://www.chromium.org/getting-involved/dev-channel). If you find a new issue, please let us know by [filing a bug](https://crbug.com/). The [community help forum](https://support.google.com/chrome/community) is also a great place to reach out for help or learn about common issues.\n\n  \n\nDaniel Yip\n\nGoogle Chrome","publishedAt":"2026-06-17T16:10:31.317Z","url":"http://chromereleases.googleblog.com/2026/06/early-stable-update-for-desktop.html","media":[],"prerelease":false,"source":{"slug":"chrome-releases","name":"Chrome Releases","type":"feed"},"product":{"slug":"chrome","name":"Chrome"},"groupSlug":"chrome","groupName":"Chrome","coverageCount":0,"contentChars":805,"contentTokens":207,"composition":null}],"pagination":{"nextCursor":"2026-06-17T16:10:31.317Z|2026-06-17T21:02:42.348Z|rel_uiDDxJRiHQvsNL4VBcPU9","limit":20}}