Terminal connector for Agent Zero. It pairs a Textual CLI with a small Agent Zero plugin so you can chat from the terminal, follow streaming events, and use the connector-specific remote editing/runtime features.

The CLI requires an Agent Zero build that includes the builtin _a0_connector plugin.

curl -LsSf https://raw.githubusercontent.com/agent0ai/a0-connector/main/install.sh | sh

irm https://raw.githubusercontent.com/agent0ai/a0-connector/main/install.ps1 | iex

a0

If you already use uv, you can install the CLI directly from a GitHub source archive. uv will pick a compatible Python for the tool environment and can download one if needed, without requiring git to be installed:

uv tool install --upgrade "a0 @ https://github.com/agent0ai/a0-connector/archive/refs/heads/main.zip"

Advanced one-off runs with uvx also work, but they are intentionally not the primary install path for this project.

If you installed a0 with the standard uv tool flow, update it in place with:

a0 update

By default a0 update follows the same main.zip channel as the installer and manual uv tool install --upgrade command above. For advanced cases you can override the package source by setting A0_PACKAGE_SPEC before running a0 update.

a0 update requires uv to be available on your PATH.

No separate plugin install is required for users once Agent Zero Core ships _a0_connector as a builtin plugin.

For Core development, keep this repo's mirror in sync with the builtin plugin directory and restart Agent Zero after changes:

cd /path/to/agent-zero
mkdir -p plugins/_a0_connector
rsync -a /path/to/a0-connector/plugin/_a0_connector/ plugins/_a0_connector/

For Docker-based Agent Zero setups, the same builtin plugin path is /a0/plugins/_a0_connector.

a0

On every launch the CLI opens the host picker first. It checks Docker for local Agent Zero containers, lists any detected WebUI endpoints as friendly URLs such as http://localhost:50001, and lets you connect explicitly with Enter or the Connect button.

If Docker finds exactly one local Agent Zero endpoint and there is no conflicting saved manual host, the CLI auto-enters that instance:

• open instance: it connects immediately
• protected instance: it advances directly to the login stage

Manual URL entry is available from the same panel for remote hosts or anything Docker cannot see. AGENT_ZERO_HOST still seeds the picker/manual URL instead of forcing an immediate connection.

Protected instances use the same web login as Agent Zero itself. The CLI posts to /login, keeps the resulting session cookie in memory for the current process, and forwards that session to /ws. Open instances skip the login stage entirely.

If you want to prefill a host, export it before starting the CLI:

export AGENT_ZERO_HOST=http://localhost:50001
a0

You can optionally remember only the chosen host in ~/.agent-zero/.env from inside the app. The CLI never stores usernames, passwords, session cookies, or connector tokens.

• 404 on /api/plugins/_a0_connector/v1/capabilities: the running Agent Zero build does not include the builtin _a0_connector plugin, or the local Core checkout/runtime copy is out of sync.
• Browser UI works but a0 does not: the core web UI can run without the connector plugin; the CLI cannot.
• Connector contract mismatch: the server is advertising an older connector auth contract. Update Agent Zero Core so its builtin _a0_connector plugin matches the CLI.
• WebSocket connection rejected: ensure proxies forward both /socket.io and /api/plugins/ unchanged, and that AGENT_ZERO_HOST exactly matches the real host seen by Agent Zero. If Docker discovery shows localhost, prefer localhost over 127.0.0.1.
• a0 update says uv is required: Install uv or rerun the existing installer.

• Configuration
• Architecture
• Development
• TUI frontend