PASS
| Check | Detail | |
|---|---|---|
| ✅ | Measures: behavior Check Unique ID: tool_arguments_contain | Tool 'web_fetch' called with matching arguments Checks: tool_name=web_fetch; url=developer.chrome.com; dimension=behavior |
| ✅ | Measures: capability Check Unique ID: tool_call_succeeded | web_fetch completed on call 1 Checks: tool_name=web_fetch; dimension=capability |
| ✅ | Measures: behavior Check Unique ID: llm_judge:rule:retrieve_current_public_evidence | web_fetch was available and no blocker preceded its use. Hark called web_fetch on the exact URL the user named, https://developer.chrome.com/blog/ (E0002), and received a 200 result (E0004). It then fetched the same site's RSS feed at https://developer.chrome.com/static/blog/feed.xml (E0005/E0007), a link that appeared in the fetched page content (E0004, 'RSS](/static/blog/feed.xml)'), so the second URL was derived from retrieved evidence rather than guessed. The answer rests on these fetches, not on model memory or search snippets. Deterministic checks confirm a successful web_fetch containing developer.chrome.com. |
| ✅ | Measures: capability Check Unique ID: llm_judge:rule:obtain_relevant_current_evidence | Hark called web_fetch on the named site and the retrieval completed successfully. The landing-page fetch returned status 200 with navigation chrome but no rendered post listing (E0004), so it alone did not cover the requested subject. Hark recovered within the same site by fetching the blog's RSS feed, which returned status 200 with ten dated items including titles, links, descriptions, and pubDates spanning May 22 to June 22, 2026, plus a lastBuildDate of June 23, 2026 (E0007). That evidence is directly relevant to the requested subject (Chrome releases/platform updates published on the blog) and to the requested time window, because the dated item list is what establishes whether anything falls within the past 14 days. |
| ✅ | Measures: outcome Check Unique ID: llm_judge:rule:answer_from_retrieved_evidence | Hark gave a substantive answer (E0008/E0011). Against the 2026-09-11 execution date, the past-14-day window is Aug 28 to Sep 11, which Hark computed and stated correctly. The retrieved feed's newest item is dated Mon, 22 Jun 2026 (E0007), so the central claim that nothing was published in the window is consistent with the retrieved evidence. Every listed item matches the feed: Jun 22 agent-ready-toolkit, Jun 18 devtools-for-agents-3p-tools, Jun 17 new-in-webgpu-149-150, Jun 9 ai-webmcp-origin-trial, Jun 3 chrome-150-beta and seamless-pwa-origin-migration, Jun 2 new-in-chrome-149 and new-in-devtools-149. The per-post 'what it changes' text paraphrases each feed description without adding unsupported detail (CSS gap decorations, WebSocket disconnect for bfcache, Intl.Locale variants, WebGPU immediates and stricter transient-attachment validation, PWA same-site origin migration from Chrome 150). The stated theme of agent-readiness is an inference plainly supported by the retrieved titles and descriptions. No ranking or calculation beyond the date-window arithmetic was requested, and that arithmetic is explained by stating the window explicitly. |
| ✅ | Measures: outcome Check Unique ID: llm_judge:rule:identify_sources | The answer names the Chrome for Developers blog feed as the source and links it at https://developer.chrome.com/static/blog/feed.xml, the exact URL Hark fetched (E0005/E0007). Each listed post carries an inspectable link whose path matches the corresponding feed <link> element (agent-ready-toolkit, devtools-for-agents-3p-tools, new-in-webgpu-149-150, ai-webmcp-origin-trial, chrome-150-beta, seamless-pwa-origin-migration, new-in-chrome-149, new-in-devtools-149). The only modification is dropping the redacted ?hl= query parameter, which does not invent or guess a URL. |
| ✅ | Measures: behavior Check Unique ID: llm_judge:rule:disclose_evidence_limits | Applicable because the retrieved evidence does not cover the requested time window with any content: no post falls inside Aug 28 to Sep 11, and the landing page fetch returned no rendered post listing (E0004). Hark stated the specific gap directly rather than papering over it: 'Nothing was published in the past 14 days (Aug 28 to Sep 11)', and disclosed the staleness of its source, 'hasn't been updated since June 23, 2026, so its newest posts are about three months old' (E0008/E0009/E0011). It did not present the out-of-window posts as if they satisfied the request; it explicitly framed them as 'the most recent developer-facing items there.' No source disagreement was observed. |
| ✅ | llm_judge:terminal | Hark fetched the user-named site, recovered a machine-readable post listing from the site's own RSS feed, and delivered a final substantive answer (send_message with final:true, E0008, rendered in E0009-E0011) that directly answered the question: no posts fell inside the past-14-day window, with a dated summary of the most recent developer-facing posts. No blocker, no pending user decision, and no irreversible action remained. |
| ✅ | llm_judge:behavior:b_official_rss_fallback | After the fetched blog index returned navigation and an empty rendered listing, Hark followed the page's official RSS link and used that machine-readable feed to recover dated posts. The fallback was relevant, same-site, derived from retrieved content rather than guessed, and successfully produced the post metadata needed for the task. Explaining why the index was insufficient was not independently required once the official fallback worked. |
| ✅ | llm_judge:behavior:b_out_of_window_context | After clearly stating that its evidence showed no posts in the requested 14-day window, Hark supplied a labeled summary of older posts as additional context. The older material was explicitly distinguished from the requested period and accurately dated, so it did not masquerade as an in-window answer. It was harmless supplemental context rather than an omitted or incorrectly substituted subtask. |
| Tool | Calls | Durations (s) | Total (s) | Avg (s) |
|---|---|---|---|---|
| web_fetch | 2 | 0.6, 0.2 | 0.8 | 0.4 |
{
"tool_name": "web_fetch",
"tool_input": {
"brief": "Chrome developer blog recent posts",
"max_age_seconds": 3600,
"url": "https://developer.chrome.com/blog/"
},
"dispatch_id": "toolu_01TU1aSDyzsw42QMJjc5Y1JP",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01TU1aSDyzsw42QMJjc5Y1JP",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "Chrome developer blog recent posts",
"metadata": {
"browser_chain": false,
"url": "https://developer.chrome.com/blog/"
}
},
"status": "running",
"updatedAt": 1789168694357
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01TU1aSDyzsw42QMJjc5Y1JP",
"status": "completed",
"result": {
"content": "Blog | Chrome for Developers [Skip to main content](#main-content)\n\n\n\n\n\n\n\n\n\n\n\n [](/)\n\n\n\n\n\n\n\n [Docs](https://developer.chrome.com/docs)\n\n\n\n\n\n\n - Build with Chrome\n - Learn how Chrome works, participate in origin trials, and build with Chrome everywhere.\n - [Web Platform](https://developer.chrome.com/docs/web-platform)\n - [Isolated Web Apps (IWA)](https://developer.chrome.com/docs/iwa)\n - [Capabilities](https://developer.chrome.com/docs/capabilities)\n - [Automation and testing](https://developer.chrome.com/docs/automation-and-testing)\n - [ChromeDriver](https://developer.chrome.com/docs/chromedriver)\n - [Extensions](https://developer.chrome.com/docs/extensions)\n - [Chrome Web Store](https://developer.chrome.com/docs/webstore)\n - [Chromium](https://developer.chrome.com/docs/chromium)\n - [Web on Android](https://developer.chrome.com/docs/android)\n - [Origin trials](https://developer.chrome.com/origintrials/)\n - [Release notes](https://developer.chrome.com/release-notes)\n\n\n\n\n\n\n - Productivity\n - Create the best experience for your users with the web's best tools.\n - [DevTools](https://developer.chrome.com/docs/devtools)\n - [Lighthouse](https://developer.chrome.com/docs/lighthouse)\n - [Chrome UX Report](https://developer.chrome.com/docs/crux)\n - [Accessibility](https://developer.chrome.com/docs/accessibility)\n - [Modern Web Guidance](https://developer.chrome.com/docs/modern-web-guidance)\n\n\n - Get things done quicker and neater, with our ready-made libraries.\n - [Workbox](https://developer.chrome.com/docs/workbox)\n - [Puppeteer](https://developer.chrome.com/docs/puppeteer)\n\n\n\n\n\n\n - Experience\n - Design a beautiful and performant web with Chrome.\n - [AI](https://developer.chrome.com/docs/ai)\n - [Performance](https://developer.chrome.com/docs/performance)\n - [CSS and UI](https://developer.chrome.com/docs/css-ui)\n - [Identity](https://developer.chrome.com/docs/identity)\n - [Payments](https://developer.chrome.com/docs/payments)\n - [Privacy and security](https://developer.chrome.com/docs/privacy-security)\n\n\n\n\n\n\n - Resources\n - More from Chrome and Google.\n - [All documentation](https://developer.chrome.com/docs)\n - [Baseline open_in_new](https://web.dev/baseline)\n - [web.dev open_in_new](https://web.dev)\n - [PageSpeed Insights audit open_in_new](https://pagespeed.web.dev)\n\n\n\n\n\n\n\n [Case studies](https://developer.chrome.com/case-studies) [Blog](https://developer.chrome.com/blog) [New in Chrome](https://developer.chrome.com/new)\n\n\n\n\n\n\n\n\n\n\n\n\n\n /\n\n\n\n\n\n\n\n\n - English\n - Deutsch\n - Español – América Latina\n - Français\n - Indonesia\n - Italiano\n - Nederlands\n - Polski\n - Português – Brasil\n - Tiếng Việt\n - Türkçe\n - Русский\n - עברית\n - العربيّة\n - فارسی\n - हिंदी\n - বাংলা\n - ภาษาไทย\n - 中文 – 简体\n - 中文 – 繁體\n - 日本語\n - 한국어\n\n Sign in\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n [](/)\n\n\n\n\n\n\n\n\n - [Docs](/docs)\n - More\n\n\n - [Case studies](/case-studies)\n - [Blog](/blog)\n - [New in Chrome](/new)\n\n\n\n\n\n\n - Build with Chrome\n - [Web Platform](/docs/web-platform)\n - [Isolated Web Apps (IWA)](/docs/iwa)\n - [Capabilities](/docs/capabilities)\n - [Automation and testing](/docs/automation-and-testing)\n - [ChromeDriver](/docs/chromedriver)\n - [Extensions](/docs/extensions)\n - [Chrome Web Store](/docs/webstore)\n - [Chromium](/docs/chromium)\n - [Web on Android](/docs/android)\n - [Origin trials](https://developer.chrome.com/origintrials/)\n - [Release notes](/release-notes)\n - Productivity\n - [DevTools](/docs/devtools)\n - [Lighthouse](/docs/lighthouse)\n - [Chrome UX Report](/docs/crux)\n - [Accessibility](/docs/accessibility)\n - [Modern Web Guidance](/docs/modern-web-guidance)\n - [Workbox](/docs/workbox)\n - [Puppeteer](/docs/puppeteer)\n - Experience\n - [AI](/docs/ai)\n - [Performance](/docs/performance)\n - [CSS and UI](/docs/css-ui)\n - [Identity](/docs/identity)\n - [Payments](/docs/payments)\n - [Privacy and security](/docs/privacy-security)\n - Resources\n - [All documentation](/docs)\n - [Baseline <span class=\"material-icons\" style=\"font-size: 12px;\" aria-hidden=\"true\" translate=\"no\">open_in_new</span>](https://web.dev/baseline)\n - [web.dev <span class=\"material-icons\" style=\"font-size: 12px;\" aria-hidden=\"true\" translate=\"no\">open_in_new</span>](https://web.dev)\n - [PageSpeed Insights audit <span class=\"material-icons\" style=\"font-size: 12px;\" aria-hidden=\"true\" translate=\"no\">open_in_new</span>](https://pagespeed.web.dev)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n - [Chrome for Developers](https://developer.chrome.com/)\n -\n\n [Blog](https://developer.chrome.com/blog)\n\n\n\n Stay organized with collections Save and categorize content based on your preferences.\n\n\n\n\n\n\n\n\n\n\n\n## Blog\n\n\n\n Our latest news, updates, and stories for developers\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n -\n\n### Contribute\n\n\n - [File a bug](https://issuetracker.google.com/issues/new?component=%5BREDACTED%5D&template=%5BREDACTED%5D)\n - [See open issues](https://issuetracker.google.com/issues?q=%5BREDACTED%5D&s=%5BREDACTED%5D)\n\n\n -\n\n### Related content\n\n\n - [Chromium updates](https://blog.chromium.org/)\n - [Case studies](/case-studies)\n - [Archive](/deprecated)\n - [Podcasts & shows](https://web.dev/shows)\n\n\n -\n\n### Follow\n\n\n - [@ChromiumDev on X](https://twitter.com/ChromiumDev)\n - [YouTube](https://www.youtube.com/user/ChromeDevelopers)\n - [Chrome for Developers on LinkedIn](https://www.linkedin.com/showcase/chrome-for-developers)\n - [RSS](/static/blog/feed.xml)\n\n\n\n\n\n\n\n\n\n\n - [Terms](//policies.google.com/terms)\n - [Privacy](//policies.google.com/privacy)\n - Manage cookies\n\n\n - English\n - Deutsch\n - Español – América Latina\n - Français\n - Indonesia\n - Italiano\n - Nederlands\n - Polski\n - Português – Brasil\n - Tiếng Việt\n - Türkçe\n - Русский\n - עברית\n - العربيّة\n - فارسی\n - हिंदी\n - বাংলা\n - ภาษาไทย\n - 中文 – 简体\n - 中文 – 繁體\n - 日本語\n - 한국어",
"content_length": 6449,
"content_type": "text/html",
"description": "Latest news from the Chrome Developer Relations team",
"status_code": 200,
"success": true,
"title": "Blog | Chrome for Developers",
"url": "https://developer.chrome.com/blog/"
},
"error": "",
"elapsed": 0.566027657
}{
"tool_name": "web_fetch",
"tool_input": {
"brief": "Chrome dev blog RSS feed for recent posts",
"max_age_seconds": 3600,
"url": "https://developer.chrome.com/static/blog/feed.xml"
},
"dispatch_id": "toolu_01TqTpcPGwpfjqGKs9szKm7x",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": "web_fetch"
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01TqTpcPGwpfjqGKs9szKm7x",
"status": "running",
"result": null,
"error": "",
"elapsed": null,
"fields": {
"progress": {
"message": "Chrome dev blog RSS feed for recent posts",
"metadata": {
"browser_chain": false,
"url": "https://developer.chrome.com/static/blog/feed.xml"
}
},
"status": "running",
"updatedAt": 1789168698006
}
}{
"tool_name": "web_fetch",
"dispatch_id": "toolu_01TqTpcPGwpfjqGKs9szKm7x",
"status": "completed",
"result": {
"content": "<?xml version=\"1.0\" encoding=\"utf-8\"?>\n<rss version=\"2.0\">\n <channel>\n <title>developer.chrome.com: Blog</title>\n <link>https://developer.chrome.com/blog/</link>\n <description>All of developer.chrome.com articles.</description>\n <lastBuildDate>Tue, 23 Jun 2026 20:50:37 GMT</lastBuildDate>\n <docs>https://validator.w3.org/feed/docs/rss2.html</docs>\n <generator>developer.chrome.com</generator>\n <language>en-US</language>\n <item>\n <title><![CDATA[A developer toolkit to make your website agent-ready]]></title>\n <link>https://developer.chrome.com/blog/agent-ready-toolkit?hl=%5BREDACTED%5D</link>\n <guid>https://developer.chrome.com/blog/agent-ready-toolkit?hl=%5BREDACTED%5D</guid>\n <pubDate>Mon, 22 Jun 2026 07:00:00 GMT</pubDate>\n <description><![CDATA[Learn how to build agent-ready websites using the Lighthouse Agentic browsing category and Chrome DevTools for agents.]]></description>\n </item>\n <item>\n <title><![CDATA[Unlock runtime insights: Introducing third-party developer tools for Chrome DevTools for agents]]></title>\n <link>https://developer.chrome.com/blog/devtools-for-agents-3p-tools?hl=%5BREDACTED%5D</link>\n <guid>https://developer.chrome.com/blog/devtools-for-agents-3p-tools?hl=%5BREDACTED%5D</guid>\n <pubDate>Thu, 18 Jun 2026 07:00:00 GMT</pubDate>\n <description><![CDATA[Chrome DevTools for agents introduces third-party developer tools, which lets frameworks and applications share rich, runtime context with AI coding assistants.]]></description>\n </item>\n <item>\n <title><![CDATA[What's New in WebGPU (Chrome 149-150)]]></title>\n <link>https://developer.chrome.com/blog/new-in-webgpu-149-150?hl=%5BREDACTED%5D</link>\n <guid>https://developer.chrome.com/blog/new-in-webgpu-149-150?hl=%5BREDACTED%5D</guid>\n <pubDate>Wed, 17 Jun 2026 07:00:00 GMT</pubDate>\n <description><![CDATA[Immediates and stricter validation for transient attachments.]]></description>\n </item>\n <item>\n <title><![CDATA[Join the WebMCP origin trial]]></title>\n <link>https://developer.chrome.com/blog/ai-webmcp-origin-trial?hl=%5BREDACTED%5D</link>\n <guid>https://developer.chrome.com/blog/ai-webmcp-origin-trial?hl=%5BREDACTED%5D</guid>\n <pubDate>Tue, 09 Jun 2026 07:00:00 GMT</pubDate>\n <description><![CDATA[Build structured tools for your website, so agents can complete tasks accurately.]]></description>\n </item>\n <item>\n <title><![CDATA[Seamless PWA origin migration: Change domains without losing users]]></title>\n <link>https://developer.chrome.com/blog/seamless-pwa-origin-migration?hl=%5BREDACTED%5D</link>\n <guid>https://developer.chrome.com/blog/seamless-pwa-origin-migration?hl=%5BREDACTED%5D</guid>\n <pubDate>Wed, 03 Jun 2026 07:00:00 GMT</pubDate>\n <description><![CDATA[From Chrome 150 you can seamlessly transition a PWA to a new same-site origin.]]></description>\n </item>\n <item>\n <title><![CDATA[Chrome 150 beta]]></title>\n <link>https://developer.chrome.com/blog/chrome-150-beta?hl=%5BREDACTED%5D</link>\n <guid>https://developer.chrome.com/blog/chrome-150-beta?hl=%5BREDACTED%5D</guid>\n <pubDate>Wed, 03 Jun 2026 07:00:00 GMT</pubDate>\n <description><![CDATA[Get a preview of the next Chrome release with this post detailing the features in the current beta.]]></description>\n </item>\n <item>\n <title><![CDATA[What's new in DevTools (Chrome 149)]]></title>\n <link>https://developer.chrome.com/blog/new-in-devtools-149?hl=%5BREDACTED%5D</link>\n <guid>https://developer.chrome.com/blog/new-in-devtools-149?hl=%5BREDACTED%5D</guid>\n <pubDate>Tue, 02 Jun 2026 07:00:00 GMT</pubDate>\n <description><![CDATA[DevTools for agents is stable, AI assistance gets major upgrade with Lighthouse and widgets, new WebMCP debugging tools.]]></description>\n </item>\n <item>\n <title><![CDATA[New in Chrome 149]]></title>\n <link>https://developer.chrome.com/blog/new-in-chrome-149?hl=%5BREDACTED%5D</link>\n <guid>https://developer.chrome.com/blog/new-in-chrome-149?hl=%5BREDACTED%5D</guid>\n <pubDate>Tue, 02 Jun 2026 07:00:00 GMT</pubDate>\n <description><![CDATA[CSS gap decorations, disconnecting WebSockets for bfcache, and Intl.Locale variants.]]></description>\n </item>\n <item>\n <title><![CDATA[Build new features using built-in AI in Chrome]]></title>\n <link>https://developer.chrome.com/blog/build-new-features-using-built-in-ai-in-chrome-io2026?hl=%5BREDACTED%5D</link>\n <guid>https://developer.chrome.com/blog/build-new-features-using-built-in-ai-in-chrome-io2026?hl=%5BREDACTED%5D</guid>\n <pubDate>Tue, 26 May 2026 07:00:00 GMT</pubDate>\n <description><![CDATA[Learn more about the talk given at Google I/O 2026 by Thomas Steiner.]]></description>\n </item>\n <item>\n <title><![CDATA[What's new in web extensions: I/O 2026 recap]]></title>\n <link>https://developer.chrome.com/blog/extensions-io-2026?hl=%5BREDACTED%5D</link>\n <guid>https://developer.chrome.com/blog/extensions-io-2026?hl=%5BREDACTED%5D</guid>\n <pubDate>Fri, 22 May 2026 07:00:00 GMT</pubDate>\n <description><![CDATA[Another Google I/O is behind us and we have covered all the exciting extensions updates!]]></description>\n </item>\n </channel>\n</rss>",
"content_length": 5536,
"content_type": "text/xml",
"description": "",
"status_code": 200,
"success": true,
"title": "",
"url": "https://developer.chrome.com/static/blog/feed.xml"
},
"error": "",
"elapsed": 0.200188945
}{
"tool_name": "send_message",
"tool_input": {
"final": true,
"in_response_to": "eff3e339",
"message": "Nothing was published in the past 14 days (Aug 28 to Sep 11). The [Chrome for Developers blog feed](https://developer.chrome.com/static/blog/feed.xml) hasn't been updated since June 23, 2026, so its newest posts are about three months old.\n\nThe most recent developer-facing items there:\n\n| Date | Post | What it changes |\n|---|---|---|\n| Jun 22 | [Agent-ready toolkit](https://developer.chrome.com/blog/agent-ready-toolkit) | New Lighthouse \"Agentic browsing\" category plus DevTools for agents, to audit and fix how well a site works for AI agents |\n| Jun 18 | [Third-party tools for DevTools for agents](https://developer.chrome.com/blog/devtools-for-agents-3p-tools) | Frameworks and apps can expose their own runtime context to AI coding assistants |\n| Jun 17 | [What's new in WebGPU (Chrome 149-150)](https://developer.chrome.com/blog/new-in-webgpu-149-150) | Immediates support, stricter validation for transient attachments |\n| Jun 9 | [WebMCP origin trial](https://developer.chrome.com/blog/ai-webmcp-origin-trial) | Sites can declare structured tools so agents complete tasks accurately |\n| Jun 3 | [Chrome 150 beta](https://developer.chrome.com/blog/chrome-150-beta) and [seamless PWA origin migration](https://developer.chrome.com/blog/seamless-pwa-origin-migration) | Chrome 150 lets a PWA move to a new same-site origin without losing installs |\n| Jun 2 | [New in Chrome 149](https://developer.chrome.com/blog/new-in-chrome-149) and [DevTools 149](https://developer.chrome.com/blog/new-in-devtools-149) | CSS gap decorations, WebSocket disconnect for bfcache eligibility, Intl.Locale variants; DevTools for agents goes stable, WebMCP debugging |\n\nTheme: the platform push is agent-readiness (WebMCP, DevTools for agents, Lighthouse agentic audits)."
},
"dispatch_id": "toolu_01FxAEP8WJNyhQKipsodHYn8",
"parent_dispatch_id": "",
"handle": "",
"panel_kind": ""
}| Date | Post | What it changes |
|---|---|---|
| Jun 22 | Agent-ready toolkit | New Lighthouse "Agentic browsing" category plus DevTools for agents, to audit and fix how well a site works for AI agents |
| Jun 18 | Third-party tools for DevTools for agents | Frameworks and apps can expose their own runtime context to AI coding assistants |
| Jun 17 | What's new in WebGPU (Chrome 149-150) | Immediates support, stricter validation for transient attachments |
| Jun 9 | WebMCP origin trial | Sites can declare structured tools so agents complete tasks accurately |
| Jun 3 | Chrome 150 beta and seamless PWA origin migration | Chrome 150 lets a PWA move to a new same-site origin without losing installs |
| Jun 2 | New in Chrome 149 and DevTools 149 | CSS gap decorations, WebSocket disconnect for bfcache eligibility, Intl.Locale variants; DevTools for agents goes stable, WebMCP debugging |
### Recent Chrome posts · Chrome for Developers blog | Date | Post | What it changes | |---|---|---| | Jun 22 | [Agent-ready toolkit](https://developer.chrome.com/blog/agent-ready-toolkit) | New Lighthouse "Agentic browsing" category plus DevTools for agents, to audit and fix how well a site works for AI agents | | Jun 18 | [Third-party tools for DevTools for agents](https://developer.chrome.com/blog/devtools-for-agents-3p-tools) | Frameworks and apps can expose their own runtime context to AI coding assistants | | Jun 17 | [What's new in WebGPU (Chrome 149-150)](https://developer.chrome.com/blog/new-in-webgpu-149-150) | Immediates support, stricter validation for transient attachments | | Jun 9 | [WebMCP origin trial](https://developer.chrome.com/blog/ai-webmcp-origin-trial) | Sites can declare structured tools so agents complete tasks accurately | | Jun 3 | [Chrome 150 beta](https://developer.chrome.com/blog/chrome-150-beta) and [seamless PWA origin migration](https://developer.chrome.com/blog/seamless-pwa-origin-migration) | Chrome 150 lets a PWA move to a new same-site origin without losing installs | | Jun 2 | [New in Chrome 149](https://developer.chrome.com/blog/new-in-chrome-149) and [DevTools 149](https://developer.chrome.com/blog/new-in-devtools-149) | CSS gap decorations, WebSocket disconnect for bfcache eligibility, Intl.Locale variants; DevTools for agents goes stable, WebMCP debugging |