CLI not authenticated

The CLI is installed but signed out. What AutoDev can tell about each CLI, what a signed-out CLI looks like in a run, and how to sign in without ever giving AutoDev a credential.

What you see #

The first-run checklist says the CLI is installed and signed out, and tells you what to do:

claude is installed but not logged in.

The manual path is Run claude in a terminal and complete the login. A signed-out codex or agy does not appear in the checklist at all. That is deliberate, and the next section says why.

In a run, a signed-out CLI shows up as a participant that does not answer. AutoDev has no separate signed-out state for a run: the CLI's turn fails, and the event log says Turn failed (infra); will retry: with what the CLI printed, or the turn ends without a post. AutoDev handles it as it handles any failing turn. It retries on a widening schedule, and after three turns in a row without a post it pauses the run and names the participant. The run stopped and why describes both. Reading the logs locates the event log.

Why #

AutoDev reads the sign-in state of claude with claude auth status --json. The answer carries whether you are logged in and your subscription type, and the check spends no model call. Any failure, such as a non-zero exit, a missing binary or a payload it cannot read, counts as unknown. It never counts as signed out.

For codex and agy, AutoDev has no sign-in check it trusts: no login-status command has been verified for codex, and agy has none to use. The checklist raises a sign-in question only when it knows you are signed out, so it stays silent about those two rather than guess.

A signed-out CLI is not a usage limit. A limit is a notice the CLI prints, that AutoDev reads, and that moves the turn to another provider or waits for the reset. A CLI that will not run at all is an infrastructure failure, and no other provider's limit changes that. Providers and failover tells the two apart.

Fix #

Sign in with the CLI itself, in a terminal, and complete its own login. On a participant's card in the CLIs destination, Open starts that CLI in an editor terminal. The login belongs to the CLI, not to AutoDev. Once claude auth status --json reports you signed in, the checklist stops asking.

AutoDev never asks for a credential and does not store one. Do not paste a token, a key or a password into the panel, into a message to the thread or into autodev providers use, which records only the path of a binary. Then send a message, or run autodev start, so the run tries again.

This page does not cover how each CLI signs in: that belongs to its vendor. If the CLI is not installed at all, No agent CLI found is the page.