Agent Zero Browser Extensions

Use this skill when the user wants to create a new Browser extension, modify an existing extension, or install a Chrome Web Store extension for Agent Zero's direct _browser plugin.

Operating Model

• Agent Zero loads Browser extensions from unpacked directories.
• Create user-owned extensions under /a0/usr/browser-extensions/<extension-slug>/.
• Browser extension paths must be visible inside the Docker runtime. Prefer /a0/usr/browser-extensions/... paths over host-only paths.
• The Browser puzzle menu can open "My Browser Extensions", seed a "+ Create New with A0" request, and install Chrome Web Store URLs.
• Chrome Web Store installs are converted into unpacked extension folders before Browser can load them.
• Extension setting changes restart active Browser runtimes so Playwright can relaunch Chromium with the extension arguments.

Safety First

Browser extensions run inside the Docker browser sandbox, but malicious or buggy extensions can still damage that sandboxed environment, corrupt browser profiles, exfiltrate page data visible to the Browser, or make browsing unreliable.

Before creating or installing an extension:

• State the requested behavior in one sentence.
• List the minimum permissions and host permissions needed.
• Avoid <all_urls> unless the user explicitly needs broad page access.
• Avoid remote code, eval-style execution, hidden credential collection, and broad network access.
• Do not store secrets in extension files.
• Prefer content scripts for page-local behavior and service workers for coordination.
• Tell the user when an extension can read or modify page content.

Create New Extension