Chrome DevTools: Google I/O AI sessions

Google’s Chrome team is steering Google I/O 2026 toward artificial intelligence coding tools inside DevTools, with sessions on agents, debugging and browser user interface work. (android-developers.googleblog.com) Google I/O runs May 19-20, 2026, with the Google keynote at 10:00 a.m. Pacific Time and the developer keynote at 1:30 p.m. Pacific Time on May 19. Google’s published schedule says Chrome is part of a two-day lineup centered on artificial intelligence, Android, Chrome and Cloud. (io.google, android-developers.googleblog.com) In Google’s own preview, one web track promises “agentic web applications,” “complex debugging workflows,” and “highly interactive UI directly in the browser.” The Chromium team’s post pointed developers to those Google I/O sessions as the place to watch for the DevTools angle. (android-developers.googleblog.com, x.com) DevTools is the inspection panel built into Google Chrome for editing pages, tracing performance and debugging network requests. Google now describes it as a place where Gemini can analyze styling, sources, network activity and performance, and where coding agents can plug in through the Model Context Protocol server. (developer.chrome.com) That shift has been unfolding in public releases for months. In Chrome 141, published in October 2025, Google introduced a preview of the Chrome DevTools Model Context Protocol server so artificial intelligence coding assistants could inspect pages in Chrome and use DevTools debugging and performance data. (developer.chrome.com) Google expanded that tooling again in Chrome 147 on April 7, 2026. The release added automatic context selection for artificial intelligence assistance, full code generation in the Console and Sources panels, Lighthouse audits inside agent workflows, memory leak detection and page routing for multi-agent work across browser tabs. (developer.chrome.com) Google has also been using I/O to turn DevTools into an artificial intelligence product showcase. At Google I/O 2025, the company highlighted artificial intelligence assistance for styling, network, sources and performance, and said developers could ask the tool to fix source code without leaving the inspected page. (io.google, developer.chrome.com) The 2026 framing goes further by tying browser debugging to “agentic coding,” Google’s term for software that can take actions across a workflow instead of only answering chat prompts. Google used the same phrase in its conference preview for the “next evolution” of developer tools. (android-developers.googleblog.com) The next test is May 19, when Google starts laying out how much of that agent workflow lives in Chrome itself and how much stays in external coding assistants. (io.google, android-developers.googleblog.com)