Connecting Your AI Agents

Zenborg automatically discovers and connects to the AI coding assistants already installed on your machine.

Instead of bundling proprietary models, Zenborg acts as a local orchestrator. It executes the official CLI binaries or communicates via the Agent Client Protocol (ACP).

Supported Native CLI Agents

Zenborg includes native adapters for the following command-line tools:

Agent Name	Executable	Provider	Primary Use
Claude Code	`claude`	Anthropic	Planning, Code Reviews, Complex Refactoring
Google Antigravity	`antigravity` / `agy`	Google	Planning, Multi-Step Tasks, Code Reviews
Gemini CLI	`gemini`	Google	Rapid Code Generation, Implementation
Hermes	`hermes`	Hermes Agent	High-turn Autonomous Worker (`--max-turns 300`)
OpenCode	`opencode`	Community	Extensible CLI Coding Workflows

Supported ACP (Agent Client Protocol) Agents

Zenborg supports editors and tools that expose the Agent Client Protocol:

Gemini CLI (ACP) (gemini-acp)
Cursor CLI (ACP) (cursor-acp)
GitHub Copilot CLI (ACP) (copilot-acp)
Kiro CLI (ACP) (kiro-acp)

ACP agents integrate directly into the loop engine, allowing you to use your editor configurations for plan reviews or code generation.

How Zenborg Detects Agents

When Zenborg starts or when you open Settings, the discovery engine scans standard executable locations.

On macOS and Linux

Zenborg inspects the user PATH environment variable as well as these specific search paths:

~/.local/bin
~/.npm-global/bin
~/.gemini/antigravity/bin
~/Library/Application Support/Antigravity/bin
~/.antigravity/bin
~/.antigravity-ide/antigravity-ide/bin
/opt/homebrew/bin
/usr/local/bin

On Windows

Zenborg inspects PATH along with common user and npm directories:

%APPDATA%\npm
%APPDATA%\Programs
%LOCALAPPDATA%\Programs
%LOCALAPPDATA%\Microsoft\WindowsApps
%USERPROFILE%\.local\bin
%USERPROFILE%\.npm-global\bin

Understanding Agent Status

In the user interface, agent health is indicated on the status dashboard:

Connected / Ready: The binary was found on your system path and passed an active probe test. Zenborg can invoke this agent for planning, execution, and reviews.
Not found: The binary is not present in any inspected directories. The agent cannot be selected in loop dropdowns until installed.

Authenticating and Troubleshooting CLI Agents

Zenborg does not collect your API keys directly for CLI tools. It relies on the authentication credentials managed by each agent’s own CLI.

If an agent displays as missing or fails during a loop stage, follow these verification steps in your terminal:

1. Claude Code

Run:

claude login

Complete the browser login to Anthropic. Verify it works by running claude "hello".

2. Google Antigravity

Ensure the antigravity or agy command is available in your PATH. If installed via npm or the official installer, verify with:

antigravity --version

3. Gemini CLI

For Gemini CLI, ensure your GEMINI_API_KEY is set in your shell environment, or run the official authentication command:

gemini auth login

4. PATH Visibility

If you can run an agent from your terminal but Zenborg reports it as not found:

Check where the binary is installed:
```
which claude
```
If installed in a non-standard directory, create a symbolic link into /usr/local/bin or ~/.local/bin:
```
ln -s "$(which claude)" ~/.local/bin/claude
```
Restart Zenborg to trigger a fresh discovery scan.

Next Steps

Once your agents are connected, configure orchestration workflows:

Learn how pipelines run in Agent Loops.
Or use agents interactively in Session Chats.