Streamlining the Developer Workflow

Chrome is actively reducing friction in the extension lifecycle by modernizing both the publishing dashboard and the underlying platform APIs.

  • Granular Dashboard Permissions: To support cross-functional teams, the Chrome Web Store Developer Dashboard now offers role-based access control. Publishers can assign specific roles—Admin, Item Manager, or Viewer—to team members, replacing the previous all-or-nothing access model at no additional cost.
  • Enterprise Publishing: External developers building bespoke enterprise solutions can now generate approval links for enterprise administrators. This allows for direct, secure publishing across domains without the operational overhead of manual side-loading or fragmented deployment policies.

Modernizing Platform APIs

Chrome is aligning its extension platform with broader web standards to simplify cross-browser development:

  • Browser Namespace Support: Chrome now supports the browser global (e.g., browser.tabs.create) alongside the traditional chrome namespace. This allows developers to write code that is more portable across Firefox and Safari.
  • Promise-based Messaging: The browser.runtime.onMessage API now supports returning promises. This eliminates the need for the sendResponse callback and the manual return of true to keep messaging ports alive, aligning Chrome with existing behaviors in other major browsers.

AI-Powered Development and Debugging

Chrome is integrating AI deeper into the development loop to handle boilerplate and verification tasks:

  • Extension Skills for AI Agents: Developers can now provide AI coding agents (like Gemini CLI or Antigravity) with "Skills" files. These files provide agents with domain-specific knowledge of the latest APIs and best practices. Crucially, these skills include instructions to generate a Chrome Web Store .md file, which automates the creation of permission justifications required during the submission process.
  • Automated Debugging with MCP: The Chrome DevTools Model Context Protocol (MCP) server now supports extension debugging. Coding agents can autonomously launch Chrome instances, install extensions, trigger actions (like clicking pop-ups), and inspect service workers or side panels. This allows for automated end-to-end testing of extension functionality directly within the agent's workflow.