{"slug": "what-s-new-in-web-extensions-i-o-2026-recap", "title": "What's new in web extensions: I/O 2026 recap", "summary": "At Google I/O 2026, Chrome announced that monthly developer registrations for extensions have more than doubled, with 17% of new extensions now using AI. Key updates include a new Modern Web Guidance skill for AI coding agents, Chrome DevTools for agent-based extension debugging, and granular member roles in the Chrome Web Store. Additionally, Chrome now supports the cross-browser `browser` namespace and offers enterprise publishing to external organizations.", "body_md": "It's that time of the year again! Google I/O 2026 has just concluded so you can check out all the biggest extension updates that Oliver and Kevin have covered in the video below.\nMore developers, more AI, more extensions\nAI is making extension development more approachable than ever. This momentum is clearly visible in our metrics: over the last year, monthly developer registrations have more than doubled. AI isn't just changing the development process, it's becoming a core feature of the extensions themselves. Currently, 17% of all extensions created for the Chrome Web Store in the past year use AI. To support the growing community of extensions developers, we are expanding developer registration to over 120 additional countries this year.\nModern Web Guidance extensions skill\nTo help developers build better extensions with AI coding agents we've created a skill for coding agents specifically designed for extension development. This skill is a part of our broader initiative, Modern Web Guidance (MWG), which provides AI coding agents with the web platform expertise, best practices, and modern API patterns.\nCheck out the developer guide for instructions on how to setup the MWG extensions skill.\nNext-level debugging with Chrome DevTools for agents\nChrome DevTools for agents is a suite of tools that brings the power of Chrome DevTools to your AI coding workflows and it now supports extension debugging.\nThis allows AI agents to perform programmatic tasks within Chrome, including:\n- Installing and uninstalling extensions.\n- Listing and reloading installed extensions.\n- Triggering extension actions and inspecting every surface, from the popup to the background service worker.\nFollow these instructions to set up Chrome DevTools for agents for extension debugging.\nExpanded member roles and permissions in Chrome Web Store\nManaging extensions in collaborative, cross-functional teams is becoming easier with several key updates to the Developer Dashboard.\nTo address the \"all-or-nothing\" access challenges that many teams face, we have introduced granular member roles. Dashboard owners can now invite team members into specific roles with a single click:\n- Admin: For those tasked with overall management and onboarding other members.\n- Item Manager: For developers who need to upload and submit extension updates.\n- Viewer: For team members who only need to monitor performance metrics.\nAdditional members can be invited to a publisher at no cost and without requiring individual developer registration. For more details, read Empower your team with expanded roles in the Developer Dashboard.\nEnterprise publishing for external organizations\nFor developers building bespoke solutions for enterprises, we've introduced a more flexible distribution model. Previously, enterprise developers could only publish extensions privately to their own enterprise. With the new private enterprise publishing option on the Chrome Web Store, developers can deploy their extensions privately to external organizations that approve them, all from within the store.\nFor more details, read New enterprise publishing option in the Chrome Web Store: Publish to external organizations.\nTransition to browser namespace\nOur commitment to a cross-browser WebExtensions platform continues with significant updates to the Chrome runtime. Chrome now supports the browser\nglobal namespace, matching the implementation in other major browsers. This shared global makes it easier for developers to build and maintain cross-browser extensions without relying on aliases.\nTo learn how to update your extension following these changes, read Transition to browser namespace.\nConclusion\nOur goal at Chrome remains to remove friction from your workflow so you can focus on building incredible experiences. Whether through expanded store permissions, modernized platform APIs, or AI-integrated tooling, we are dedicated to elevating the extension developer experience. We can't wait to see what you build next.", "url": "https://wpnews.pro/news/what-s-new-in-web-extensions-i-o-2026-recap", "canonical_source": "https://developer.chrome.com/blog/extensions-io-2026?hl=en", "published_at": "2026-05-22 07:00:00+00:00", "updated_at": "2026-05-24 05:06:04.920691+00:00", "lang": "en", "topics": ["artificial-intelligence", "developer-tools", "products"], "entities": ["Google I/O", "Chrome Web Store", "Modern Web Guidance", "Chrome DevTools"], "alternates": {"html": "https://wpnews.pro/news/what-s-new-in-web-extensions-i-o-2026-recap", "markdown": "https://wpnews.pro/news/what-s-new-in-web-extensions-i-o-2026-recap.md", "text": "https://wpnews.pro/news/what-s-new-in-web-extensions-i-o-2026-recap.txt", "jsonld": "https://wpnews.pro/news/what-s-new-in-web-extensions-i-o-2026-recap.jsonld"}}