zed-industries/zed · error · AuthenticateError

sign-in did not complete: {current_status:?}

Error message

sign-in did not complete: {current_status:?}

What it means

authenticate spawns a watcher that waits for the client status to leave the signing-in state and for a current user to appear; if the sign-in flow ends in any terminal state other than signed-in (or the user watch never resolves), the wait gives up with this error. It means the sign-in did not finish successfully, not a transport failure.

Source

Thrown at crates/language_models/src/provider/cloud.rs:350

        }
        let mut status = self.state.read(cx).client.status();
        let mut current_user = self.state.read(cx).user_store.read(cx).watch_current_user();
        if !status.borrow().is_signing_in() {
            return Task::ready(Ok(()));
        }
        cx.background_spawn(async move {
            while status.borrow().is_signing_in() {
                status.next().await;
            }
            while current_user.borrow().is_none() {
                let current_status = *status.borrow();
                if !matches!(
                    current_status,
                    client::Status::Authenticated
                        | client::Status::Reauthenticated
                        | client::Status::Connected { .. }
                ) {
                    return Err(AuthenticateError::Other(anyhow!(
                        "sign-in did not complete: {current_status:?}"
                    )));
                }
                futures::select_biased! {
                    _ = current_user.next().fuse() => {},
                    _ = status.next().fuse() => {},
                }
            }
            Ok(())
        })
    }

    fn settings_view(&self, cx: &mut App) -> Option<ProviderSettingsView> {
        let state = self.state.read(cx);
        let user_store = state.user_store.read(cx);
        let is_zed_model_provider_enabled = user_store
            .current_organization_configuration()
            .map_or(true, |config| config.is_zed_model_provider_enabled);

View on GitHub (pinned to 9d272b0363)

Solutions

  1. Retry the Zed Cloud sign-in flow
  2. Check network/proxy connectivity to Zed's cloud services
  3. Sign in via the account menu and complete the browser flow
Defensive patterns

Strategy: retry

When it happens

Trigger: Thrown at crates/language_models/src/provider/cloud.rs:350 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of zed-industries/zed@9d272b0363 (2026-08-20). Data as JSON: /api/errors/ec88edc2f6080e03. Report an issue: GitHub.