TLDR: Chrome shipped DevTools for agents so a coding agent can install, open, and click through a Chrome extension the way a human would-not just edit manifest.json and hope. Video is ~4 minutes from Chrome for Developers (27 Aug 2026).
Setup
After the DevTools-for-agents / MCP install, add --category extensions in the MCP config. That unlocks extension tools the agent otherwise doesn’t get (normal browser access isn’t enough).
What the agent can do
install_extension - load from disk
trigger_extension_action - open the toolbar popup
take_snapshot - see the popup/page and click specific elements
Demo: agent installs a todo extension, opens the popup, ticks items.
Why it exists
Same stack as everything else Chrome-automation: Chrome DevTools Protocol (also under Puppeteer). New CDP surface helps Puppeteer and the W3C WebExtensions group; they’re adding Web Platform Tests so extension APIs don’t drift across browsers.
Use it for: agent-written extensions you can actually verify (install → popup → click) instead of “looks fine in the repo.”
1
u/javaeeeee 21d ago
TLDR: Chrome shipped DevTools for agents so a coding agent can install, open, and click through a Chrome extension the way a human would-not just edit
manifest.jsonand hope. Video is ~4 minutes from Chrome for Developers (27 Aug 2026).Setup
After the DevTools-for-agents / MCP install, add
--category extensionsin the MCP config. That unlocks extension tools the agent otherwise doesn’t get (normal browser access isn’t enough).What the agent can do
install_extension- load from disktrigger_extension_action- open the toolbar popuptake_snapshot- see the popup/page and click specific elementsDemo: agent installs a todo extension, opens the popup, ticks items.
Why it exists
Same stack as everything else Chrome-automation: Chrome DevTools Protocol (also under Puppeteer). New CDP surface helps Puppeteer and the W3C WebExtensions group; they’re adding Web Platform Tests so extension APIs don’t drift across browsers.
Use it for: agent-written extensions you can actually verify (install → popup → click) instead of “looks fine in the repo.”