zed-industries/zed · error

launch request failed

Error message

launch request failed

What it means

The POST to the browser companion's /launch-and-attach endpoint failed at the transport level (send returned Err), so the browser debug target was never launched. The companion is up but the request itself failed — connection reset, shutdown, or malformed serialization.

Source

Thrown at crates/project/src/debugger/session.rs:3071

                                .await
                                .ok();
                            line.clear();
                        }
                    }));
                }
                background_tasks.push(cx.spawn({
                    let mut console_output = console_output.clone();
                    async move |_| match companion_process.status().await {
                        Ok(status) => {
                            if status.success() {
                                console_output
                                    .send("Companion process exited normally".into())
                                    .await
                                    .ok();
                            } else {
                                console_output
                                    .send(format!(
                                        "Companion process exited abnormally with {status:?}"
                                    ))
                                    .await
                                    .ok();
                            }
                        }
                        Err(e) => {
                            console_output
                                .send(format!("Failed to join companion process: {e}"))
                                .await
                                .ok();
                        }
                    }
                }));
            }

            // TODO pass wslInfo as needed

            let companion_address = format!("127.0.0.1:{companion_port}");

View on GitHub (pinned to 9d272b0363)

Solutions

1. Retry the launch; transient connection resets to the companion are common
2. Restart the browser companion if it keeps failing, and confirm the companion browser extension is still connected

When it happens

Trigger: Thrown at crates/project/src/debugger/session.rs:3039 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/d0f5836028498323. Report an issue: GitHub.