Guide the user through installing and connecting the A0 CLI on the host machine so Dockerized Agent Zero can work on real local files. Use when asked to install A0, set up the CLI connector, connect Agent Zero to local files, or troubleshoot host-vs-container setup confusion.
Use this skill to guide the user through installing a0 on their host machine and connecting it to Agent Zero.
a0 installs and runs on the user's host machine.Start here:
Have you already tried installing
a0? If so, what command did you run, where did you run it, and what happened?
If they already tried, diagnose that attempt before repeating instructions.
If the user is inside the Agent Zero container, /a0, docker exec, or another sandbox shell, stop and say:
a0does not get installed inside the Agent Zero container. Exit to your normal host terminal first. Agent Zero stays in Docker;a0belongs on your machine.
Do not keep giving install commands until they are back on the host.
If the platform is unclear, ask one short question:
Are you on macOS/Linux shell or Windows PowerShell on the host machine?
Then use the matching installer.
Treat these public installer URLs as placeholders for now. Use them first, but be ready to switch to the manual uv tool install path if the raw GitHub URL is blocked, private, or unreachable.
macOS / Linux:
curl -LsSf https://raw.githubusercontent.com/agent0ai/a0-connector/main/install.sh | sh
Windows PowerShell:
irm https://raw.githubusercontent.com/agent0ai/a0-connector/main/install.ps1 | iex
The installer will install uv if needed, then run uv tool install --upgrade <package-spec> for the CLI.
uv tool install fallback when neededIf the placeholder installer URL is unavailable, switch to a manual uv tool install flow instead of stopping.
Public Git fallback:
uv tool install --upgrade git+https://github.com/agent0ai/a0-connector
Local checkout or internal mirror examples:
uv tool install --upgrade /path/to/a0-connector
uv tool install --upgrade git+ssh://git.example.com/team/a0-connector.git
If they want to reuse the stock installer with a custom package source, explain that the installer honors A0_PACKAGE_SPEC.
a0After install, the next step is always:
a0
If the command is not found yet, tell them to open a new terminal and run a0 again.
Tell the user what to expect:
a0 opens the host picker first.a0 may discover it automatically.http://localhost:50001, or a tunnel URL.Settings > External Services > Flare Tunnel, click Create Tunnel, then copy and paste the HTTPS URL into a0 exactly as shown.https://example.trycloudflare.com do not need a port appended.AGENT_ZERO_HOST can prefill the target host without bypassing the picker.Example:
export AGENT_ZERO_HOST=http://localhost:50001
a0
Tunnel example:
export AGENT_ZERO_HOST=https://example.trycloudflare.com
a0
Successful setup looks like this:
a0 starts on the host machine./a0 paths, redirect them to the host-machine install.a0 gets a connector 404, explain that the running Agent Zero build likely does not include the builtin _a0_connector support yet and should be updated.a0 does not, remind them the web UI can run without connector support but the CLI cannot.host:port, or create a Flare Tunnel in Settings > External Services > Flare Tunnel and paste that HTTPS URL directly.User: "Help me set up the A0 CLI connector."
Respond like this:
a0.User: "I'm inside the Agent Zero container. How do I install A0?"
Respond like this:
a0 must be installed on the host, not in the container.User: "The raw GitHub installer URL is blocked on our network."
Respond like this:
uv tool install --upgrade <package-spec> flow.a0 and connect to Agent Zero.