CLI bridging setup

SwarmADE ships no model of its own. Instead it bridges the AI coding CLIs you already run as Workers in your Hive. Bridging is deliberately thin: during the Pre-flight Wizard, SwarmADE scans your PATH for each supported CLI binary, lists the ones it finds, and lets you enable them. You keep your own authentication — your subscription, API keys, and login session stay inside each CLI, exactly as they work when you use the tool standalone.

Because the model usage lives inside your CLI, a Worker only appears in SwarmADE once the underlying command runs cleanly in your terminal. The verification snippets below each check two things: that the binary is on your PATH, and that it reports a version (which usually means it is installed and ready to authenticate).

Worker CLI calls do not consume Honey. They bill against your own CLI subscription or keys. Honey is only spent on server-side work — Queen planning, Drone reviews, and SwarmMemory cloud sync and semantic search.

Claude

Anthropic’s coding CLI, invoked as claude. SwarmADE detects it by finding claude on your PATH.


command -v claude && claude --version

Codex

OpenAI’s coding CLI, invoked as codex. Detected when codex resolves on your PATH.


command -v codex && codex --version

opencode

An open-source terminal coding agent, invoked as opencode. Detected on your PATH.


command -v opencode && opencode --version

Aider

A terminal pair-programming CLI, invoked as aider. Detected on your PATH.


command -v aider && aider --version

Cline

An autonomous coding agent CLI, invoked as cline. Detected on your PATH.


command -v cline && cline --version

Goose

An extensible on-machine coding agent, invoked as goose. Detected on your PATH.


command -v goose && goose --version

Cursor

The Cursor CLI, invoked as cursor. Detected on your PATH.


command -v cursor && cursor --version

After detection

If a command prints a path and a version, SwarmADE will list it in the Pre-flight Wizard, ready to enable as a Worker. If it prints nothing, fix your PATH or reinstall the CLI, then reopen the Wizard. For the broader setup flow, see Bringing Your CLI. To understand how SwarmADE actually drives each bridged CLI process, read the Local PTY model.