warpdotdev/warp · error

Authentication failed: {err:#}

Error message

Authentication failed: {err:#}

What it means

The auth flow itself failed (AuthFailed(err)) — distinct from NeedsReauth: this wraps transport and server failures such as network errors, 5xx responses, or unexpected auth-server responses from authenticate_api_key or refresh_user. The underlying chain is printed with {err:#}.

Source

Thrown at app/src/ai/agent_sdk/mod.rs:1713

            AuthManagerEvent::AuthComplete => {
                dispatched = true;
                if let Err(err) = dispatch_command(ctx, command.clone(), global_options.clone()) {
                    report_fatal_error(err, ctx);
                }
            }
            AuthManagerEvent::NeedsReauth => {
                dispatched = true;
                let auth_state = AuthStateProvider::handle(ctx).as_ref(ctx).get();
                let message = if auth_state.is_api_key_authenticated() {
                    "Your API key is invalid. Please provide a valid key via '--api-key' or the WARP_API_KEY environment variable.".to_string()
                } else {
                    format!("Your credentials are invalid. Please log in again with `{cli_name} login`.")
                };
                report_fatal_error(anyhow::anyhow!(message), ctx);
            }
            AuthManagerEvent::AuthFailed(err) => {
                dispatched = true;
                report_fatal_error(anyhow::anyhow!("Authentication failed: {err:#}"), ctx);
            }
            _ => {}
        }
    });

    // Trigger authentication - the subscription above will handle the result.
    AuthManager::handle(ctx).update(ctx, |auth_manager, ctx| match authentication {
        CommandAuthentication::PendingApiKey(api_key) => {
            auth_manager.authenticate_api_key(api_key, ctx);
        }
        CommandAuthentication::RefreshUser => auth_manager.refresh_user(ctx),
    });
}

/// Check if we're running within Warp (for example, if this is an invocation of the Warp CLI
/// within a Warp terminal session).
pub fn is_running_in_warp() -> bool {
    std::env::var("TERM_PROGRAM")

View on GitHub (pinned to e72fd7aacb)

Solutions

1. Verify connectivity to the configured server root URL (curl its health endpoint)
2. Retry after transient network issues
3. Check proxy/egress rules allow the warp-server domains
4. Re-run with verbose logging and read the appended {err} chain to identify the failing hop

# Distinguish transport failure from credential rejection before retrying
curl -fsS --max-time 10 "$SERVER_ROOT_URL" >/dev/null 2>&1 || { echo 'server unreachable' >&2; exit 1; }

out=$(warp agent list 2>&1) || { case "$out" in
  *'Authentication failed:'*) retry_with_backoff warp agent list ;;
  *'API key is invalid'*|*'credentials are invalid'*) warp login ;;
  *) echo "$out" >&2; exit 1 ;;
esac; }

When it happens

Trigger: An auth-required command when the CLI cannot reach the auth/warp-server endpoints: DNS failure, offline machine, proxy blocking the request, server outage, or a malformed/unexpected server response.

Common situations: CI runners with egress restrictions; network flaps; warp-server incidents; TLS-intercepting middleboxes breaking the auth handshake.

Understand the failure class

• Authentication and authorization failures — expired tokens, bad credentials, and missing scopes.

Related errors

• Timed out establishing IAP access to warp-server.
• Error polling OAuth status: {err}
• Could not retrieve the agent-mode model list from the server
• Timed out refreshing team metadata
• Failed to fetch images

AI-assisted analysis of warpdotdev/warp@e72fd7aacb (2026-08-16). Data as JSON: /api/errors/ff8808eac20620bb. Report an issue: GitHub.