xai-org/grok-build · error

failed to start or connect to leader: {e}

Error message

failed to start or connect to leader: {e}

What it means

Error "failed to start or connect to leader: {e}" thrown in xai-org/grok-build.

Source

Thrown at crates/codegen/xai-grok-pager-bin/src/main.rs:650

    ensure_authenticated(
        &agent_config.grok_com_config,
        false,
        Some("No cached credentials found. Run `grok login` first."),
    )
    .await?;
    let env_urls = LeaderEnvUrls::from(&agent_config.grok_com_config);
    let capabilities = ClientCapabilities {
        client_version: Some(PAGER_CLIENT_VERSION.to_string()),
        ..Default::default()
    };
    let conn = connect_or_spawn(
        "grok-workspace-cli",
        ClientMode::Stdio,
        &env_urls,
        capabilities,
    )
    .await
    .map_err(|e| anyhow::anyhow!("failed to start or connect to leader: {e}"))?;
    drop(conn);
    let target = LeaderTargetArgs::default();
    let client = connect_workspace_control(&agent_config, &target).await?;
    ensure_workspace_caps(client.registration())?;
    if restart {
        let _ = client.send_control(ControlCommand::WorkspaceStop).await;
    }
    let cwd = match args.cwd {
        Some(p) => p,
        None => std::env::current_dir()
            .map_err(|e| anyhow::anyhow!("cannot determine current directory: {e}"))?,
    };
    let cwd = std::path::absolute(&cwd).unwrap_or(cwd);
    let payload = client
        .send_control(ControlCommand::WorkspaceStart {
            hub_url: args.hub_url.clone(),
            cwd: cwd.display().to_string(),
        })

View on GitHub (pinned to bc7f02eddd)

When it happens

Trigger: Thrown at crates/codegen/xai-grok-pager-bin/src/main.rs:650 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of xai-org/grok-build@bc7f02eddd (2026-08-31). Data as JSON: /api/errors/21e7dfebd7ac75a8. Report an issue: GitHub.