Supported Agents

AuraManager's aura CLI is an agent management tool — it discovers, registers, and executes AI coding agents on your local machine. The daemon scans your PATH for installed agent CLIs, runs version detection (<binary> --version), and registers each valid agent as a runtime in your workspace.

Not every agent with code in the repository is currently verifiable end-to-end. The tables below distinguish between agents whose full pipeline has been confirmed working, agents the daemon can detect but cannot yet register (known limitations), and agents whose backend adapter exists but has not been verified on the reference setup.

Verified Working

These 7 agents have been confirmed working through the full pipeline: daemon detects the binary, version detection passes, and the runtime registers successfully. They are ready for production use.

Agent Reference

Verifying After Install

After installing an agent, confirm the full Aura pipeline works:

# 1. Verify the binary is on PATH and --version returns semver
<binary> --version

# 2. If the daemon was already running, restart it to pick up the new binary
aura daemon restart

# 3. Check the daemon detected the agent
aura daemon status
# Look for the agent name in the "Agents:" line

# 4. Confirm the runtime is registered
aura runtime list
# Look for a runtime with the agent's provider type and status "online"

If <binary> --version succeeds but the agent does not appear in aura daemon status, the daemon may not see the same PATH. On macOS/Linux, GUI-launched daemons may miss bins installed by version managers (fnm, nvm, mise). Set the explicit path with the corresponding AURA_<AGENT>_PATH environment variable (see Configuration), restart the daemon, and check again.

Daemon Detects but Registration Fails

These agents are found on PATH and appear in aura daemon status, but the daemon cannot complete registration. They are not usable as runtimes until the underlying issue is resolved.

Code Adapter Exists — Not Verified on This Setup

These agents have backend implementations in the codebase (server/pkg/agent/). The daemon can theoretically detect them if their binary is installed on PATH, and the adapter should execute them. They have not been verified end-to-end on the reference macOS setup because the binary is not installed.

They are not "supported" in the sense of a guaranteed working product experience — they are "implemented" and await verification.

Known Not Supported

These tools are not CLI-based coding agents. They cannot be detected or managed by the Aura daemon, and there is no code adapter for them. Do not expect them to appear in aura daemon status or aura runtime list.

If a tool provides a headless CLI binary that supports non-interactive execution with structured output, it can potentially be added to AuraManager. See the open-platform page for custom runtime profiles.

How Detection and Registration Work

PATH scan → exec.LookPath → version detection (--version) → min version check → server registration

1. PATH scan: The daemon probes PATH (and login shell PATH on macOS/Linux) for each known binary name.
2. Version detection: Runs <binary> --version and parses the output for a semver string (e.g. 2.1.98). If --version fails or the output has no semver token, the agent is skipped.
3. Minimum version check: A few agents enforce a minimum CLI version (see below). Most agents have no minimum.
4. Server registration: The daemon sends the agent name, version, and device info to the AuraManager server, which creates or updates the runtime record.

Agents can also be registered through custom runtime profiles (aura profile), which let you define a protocol_family (matching any supported agent type) and a custom command_name. This is the extension point for agents not in the built-in list.

Minimum Version Requirements

Configuration

Agent Binary Paths

By default, the daemon discovers agent CLIs on your PATH. Override the path for any agent with environment variables:

Model Overrides

Each agent's model can be overridden via AURA_<AGENT>_MODEL (e.g. AURA_CLAUDE_MODEL=claude-sonnet-4-6). The value is passed to the agent's --model flag. See the table above for the full list of variables.

Default CLI Arguments

Some agents support default extra arguments via AURA_<AGENT>_ARGS:

Arguments are POSIX shellword-parsed and applied in this order: hardcoded AuraManager defaults → daemon-wide env defaults → per-task custom_args.

Getting Started

1. Install one or more agent CLIs on your machine (start with one from the Verified Working list).
2. Run aura setup to configure and start the daemon.
3. Check aura daemon status to confirm detection, and aura runtime list to confirm registration.
4. Assign tasks to agents in your AuraManager workspace.

For full CLI installation and daemon configuration details, see the CLI and Daemon Guide.