Build and test Chrome extensions with an agent
When your project is a Chrome extension, the agent can load it into a real Chrome, click through it, take screenshots and fix what breaks, without you testing by hand.
When a session works on a Chrome extension, this feature lets the agent test its own work: it loads the extension into a real Chrome, opens the popup, takes screenshots, reads errors and reloads after each change.
This feature is in Preview: it is still in development and off until you turn it on.
Turn it on#
Open Settings > Lab and turn on Chrome extension dev (Autopilot).
Open Agent Tools > CLI Tools, find agent-browser and click Install. It also downloads a separate test copy of Chrome.
Open your extension's project and start a session as usual.
From then on, any session in a project with a Chrome extension manifest.json gets the testing steps added to its instructions.
Keep your extensions in one place#
Developer Tools > Extensions in the sidebar opens the Chrome Extensions hub. It lists your extension projects, each marked Tested (the agent has tested it) or Draft, with three buttons:
Open switches to the project.
Test it starts a session that tests the extension (it asks first).
Install in Chrome shows you how to load it into your own Chrome. It works only after a successful test.
Click New Extension to start a guided mission that sets up a new extension and hands it to a session that builds and tests it. Right-click a row to Rename or Remove it from the hub.
Install it in your own Chrome#
Yardmaster never installs an extension into your Chrome for you; Chrome requires you to do that. Install in Chrome walks you through it: click Reveal folder, open chrome://extensions in Chrome, turn on Developer mode (top right), then click Load unpacked and pick that folder.
The settings file. Yardmaster adds an
agent-browser.jsonfile to the project so the test Chrome opens visibly with your extension loaded. Git is told to ignore it, so it is never committed.What it does not do. It does not publish to the Chrome Web Store, and it does not handle Firefox or Safari extensions.
Reminder card. If you open an extension project before installing agent-browser, one Inbox card suggests setting it up. Its text points to a Set it up for me button in Settings that does not exist; install agent-browser from CLI Tools as above instead.