Documentation
A0 CLI Connector
Connect Agent Zero to your terminal, local project files, and approved browser while Agent Zero stays safely sandboxed in Docker.
- Install A0 CLI on the host machine
- Connect to the running Agent Zero Web UI
- Work with local files and terminal controls
- Use Bring Your Own Browser when a browser profile should stay on your computer
Install A0 CLI
Run the installer on your host computer, not inside the Agent Zero container.
macOS / Linux
curl -LsSf https://cli.agent-zero.ai/install.sh | sh
Windows PowerShell
irm https://cli.agent-zero.ai/install.ps1 | iex
Open It And Connect
- Make sure Agent Zero is already running.
- Run
a0on your host machine. - If Agent Zero is on the same computer, click Connect in the host picker.
- If Agent Zero is somewhere else, choose Enter URL manually and paste the Web UI address.
- Open or create a chat and confirm you can talk to Agent Zero from the terminal.
Useful launch options
a0 --host http://localhost:32080
a0 --no-auto-connect
a0 --no-docker-discovery
You can also set AGENT_ZERO_HOST=http://localhost:32080 before launching a0.
Use The Connected Shell
After connecting, the shell shows the Agent Zero address, active project, selected model, local folder, Agent Zero workspace, and message box.
| Key | Action |
|---|---|
F3 | Toggle host file read/write access for the active CLI session. |
F4 | Toggle remote code execution through the active CLI session. |
F5 | Clear the visible chat log. |
F6 | Open the chat list. |
F7 | Nudge the active agent run. |
F8 | Pause the active agent run. |
Ctrl+P | Open the command palette. Use this if your terminal captures function keys. |
Slash Commands
Type a slash command in the message box and press Enter. Most commands are also available from Ctrl+P.
| Command | Use it for |
|---|---|
/new | Create a new empty chat. |
/chats | List previous chats. |
/project | Open the project menu or switch directly with /project <name>. |
/profile | Pick or set the active Agent Profile. |
/presets | Choose a model preset. |
/models | Edit the active models. |
/browser | Check or change Browser mode. |
/attach | Attach local image files to the next message. |
/pause, /resume, /nudge | Control the active run. |
Bring Your Own Browser
Bring Your Own Browser lets Agent Zero use Chrome, Edge, or Chromium on your computer through A0 CLI. Use it when a page, login, or browser profile should stay on your machine. Once A0 CLI is connected and host browser mode is active, you can start and steer the host browser from either A0 CLI or the Agent Zero Web UI.
- Keep A0 CLI connected to the Agent Zero chat.
- In Browser settings, choose Bring Your Own Browser.
- If you want Agent Zero to use an already-open Chrome window, open that browser first.
- Go to
chrome://inspect/#remote-debugging. - Enable Allow remote debugging for this browser instance.
Important: remote debugging grants control of that browser session, including saved data, cookies, site data, and navigation. Use it only with trusted Agent Zero instances and browser windows you intend Agent Zero to control.
Helpful browser commands
/browser status
/browser host on
/browser relaunch
/browser container
/browser privacy reminds you how page text and screenshots are allowed to flow. Visit the Web UI to change the policy to local models only or be warned when using cloud LLMs. Use /browser relaunch when you want to manually open or relaunch the host browser and trigger the browser approval prompt.
Give Setup To Another Agent
If another agent is helping, paste one short setup brief instead of a long checklist.
Set up the A0 CLI connector for Agent Zero on this machine using the a0-setup-cli Skill.
Troubleshooting
- Nothing appears locally: enter the Agent Zero web address manually or set
AGENT_ZERO_HOST. - You installed from inside Docker: install A0 CLI on the host machine instead. Agent Zero stays in Docker.
- Function keys do nothing: use
Ctrl+P; some IDE terminals capture function keys. - Connector support is missing: update Agent Zero first.
- Host browser cannot start: keep A0 CLI connected, verify Browser location is Bring Your Own Browser, and run
/browser status.