Choose the internal Docker browser or a browser on the computer running A0 CLI.
deployed_codeInternal Docker browser selected. Host-browser CLI settings are ignored for Browser tool runs.
info
For an already-open browser, Chrome, Edge, Brave, Vivaldi, and Chromium use chrome://inspect/#remote-debugging; Opera uses opera://inspect/#remote-debugging. Enable "Allow remote debugging for this browser instance", then restart or reconnect A0 CLI if the browser does not appear. If needed, launch the browser with --remote-debugging-port=9222 and --user-data-dir=<profile-dir>, or set A0_HOST_BROWSER_REMOTE_DEBUGGING_ENDPOINTS to the full ws://.../devtools/browser/... endpoint.
warning
Existing profile lets the agent interact with the browser instance you authorize,
including signed-in sites, cookies, tabs, downloads, and page content.
Browsing
Set how new Browser sessions start and how an already-open Browser surface follows agent activity.
Extensions
Choose which installed Chrome extensions Browser loads.
warning
Extensions run inside the Docker browser sandbox, but malicious or buggy extensions can
still damage that environment. Keep only the extensions you trust enabled.