No agent CLI found

The panel opens and nothing runs. AutoDev drives a CLI that is already on your machine, and it does not bundle one. How it looks for claude, codex and agy, and how to point it at one it cannot see.

What you see #

The panel opens, and nothing runs. Its first-run checklist lists the missing CLI:

claude is not installed. AutoDev orchestrates your own authenticated CLI — it does not bundle one.

The checklist adds what to do, Install claude and reopen this panel. It says the same for codex. agy is optional, so the checklist says nothing about it when it is missing.

The CLIs destination shows the same fact on a participant's card. A participant whose CLI is missing reads <provider> is not available on this machine., with two buttons: Copy install and Adopt a binary…. The first copies the vendor's install command for claude or codex to the clipboard, and AutoDev does not run it. The second is below.

A run whose team includes a missing CLI fails that participant's turns, with Turn failed (infra); will retry: in the event log. AutoDev retries on a schedule, and then pauses. The run stopped and why has the schedule.

Why #

AutoDev checks each CLI by running claude --version, codex --version or agy --version. A command that exits with code 0 counts as installed. Anything else counts as missing.

The command it runs is the CLI's own name, found on the PATH of the process that started AutoDev, unless you have adopted a binary for that provider. A VS Code that was open before the install, or a portable copy that is not on the PATH, is a common reason for a CLI you can run and AutoDev cannot.

AutoDev does not call a model API and does not bundle an agent. Without one of the three, it has nothing to drive.

Fix #

Run the same check in a terminal. If it does not exit with code 0, the CLI is missing or broken:

claude --version

Install the CLI, then reopen the panel. When nothing else is outstanding, the checklist says Ready. If the checklist next says the CLI is not logged in, CLI not authenticated is the page.

When the CLI runs in your terminal and the panel still calls it missing, tell AutoDev where it is. On the participant's card, press Adopt a binary…, choose the file, and the panel answers Using <path>. From a terminal:

autodev providers use claude <path-to-claude>

AutoDev records the path, on the machine, and every turn and every terminal it opens for that provider uses that file. It records nothing else about the CLI. autodev providers lists what has been recorded, one line per provider as <provider>: <path>, or PATH when none was given, and it prints No providers adopted on this machine. when the list is empty, which is normal when the CLIs are on the PATH. It does not check that the files run.

This page does not cover how to install claude, codex or agy: each belongs to its own vendor. Requirements lists what AutoDev expects to find.