warpdotdev/warp · error · anyhow::Error

Server error: did not receive auth URL for OAuth flow

Error message

Server error: did not receive auth URL for OAuth flow

What it means

Defensive server-contract error in auth_repos_then_execute: the auth status response had blocking private-repo issues and included a tx_id but no auth_url. The match on (response.auth_url, response.tx_id) treats (None, Some(_)) as an unexpected server response — the client needs the URL to direct the user to the browser flow, so it aborts with 'Server error: did not receive auth URL for OAuth flow'.

Source

Thrown at app/src/ai/agent_sdk/environment.rs:697

                                        }
                                    }
                                },
                            );
                        }
                        (Some(auth_url), None) => {
                            // Legacy flow: no txId, print URL and exit.
                            println!("\nAuthorize access here: {auth_url}\n");
                            println!("After authorizing, please re-run this command.");
                            ctx.terminate_app(
                                warpui::platform::TerminationMode::ForceTerminate,
                                None,
                            );
                        }
                        (None, Some(_)) => {
                            // Server returned txId without authUrl - unexpected.
                            ctx.terminate_app(
                                warpui::platform::TerminationMode::ForceTerminate,
                                Some(Err(anyhow::anyhow!(
                                    "Server error: did not receive auth URL for OAuth flow"
                                ))),
                            );
                        }
                        (None, None) => {
                            // No auth URL or txId provided, but we have auth issues.
                            ctx.terminate_app(
                                warpui::platform::TerminationMode::ForceTerminate,
                                Some(Err(anyhow::anyhow!(
                                    "Cannot {} environment: authorization required but no auth flow provided by server",
                                    operation_name
                                ))),
                            );
                        }
                    }
                }
                Err(e) => {
                    ctx.terminate_app(

View on GitHub (pinned to e72fd7aacb)

Solutions

1. Update the Warp client (and, for self-hosted setups, warp-server) so both sides agree on the auth response contract
2. Retry — if it was a transient partial outage the full response usually comes back
3. For local server development, verify the check_user_repo_auth_status resolver returns authUrl alongside txId
4. Report with the server version if it reproduces — this arm exists to catch exactly this mismatch

// For self-hosted setups: confirm client and warp-server versions match before
// running private-repo create flows (the authUrl+txId pair must be served together).

(None, Some(_)) => {
    // server returned txId without authUrl: retry once, then update client/server
    // and report if the response shape keeps missing authUrl
}

When it happens

Trigger: A warp-server version that returns a connect transaction ID without the authorization URL (schema/behavior change or partial outage); middleware stripping fields from the GraphQL response; client/server version skew where the server's response shape no longer matches the client's expectations.

Common situations: Running a newer CLI against an older self-hosted warp-server (or vice versa); local dev with WITH_LOCAL_SERVER pointing at a modified server build; server bugs during incidents that populate txId but drop authUrl.

Related errors

• Unexpected OAuth status
• failed to create API key
• failed to expire API key
• Failed to fetch images
• Failed to fetch images: {}

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