zed-industries/zed · error · anyhow::Error

{adapter}: is not a valid adapter name

Error message

{adapter}: is not a valid adapter name

What it means

resolve_scenario failed to resolve the debug scenario's adapter name to a configured debug adapter; the message names the unknown adapter. The `adapter` field in the scenario/task JSON does not match any registered adapter.

Source

Thrown at crates/debugger_ui/src/session/running.rs:1260

                            .map(|err| err.to_string())
                            .unwrap_or_default())
                    })?;
                let request = dap_store
                    .update(cx, |this, cx| {
                        this.run_debug_locator(&locator_name, task, cx)
                    })?
                    .await?;

                let zed_config = ZedDebugConfig {
                    label: label.clone(),
                    adapter: adapter.clone(),
                    request,
                    stop_on_entry: None,
                };

                let scenario = dap_registry
                    .adapter(&adapter)
                    .with_context(|| anyhow!("{adapter}: is not a valid adapter name"))?.config_from_zed_format(zed_config)
                    .await?;
                config = scenario.config;
                util::merge_non_null_json_value_into(extra_config, &mut config);

                Self::substitute_variables_in_config(&mut config, &task_context);
            } else {
                let Err(e) = request_type else {
                    unreachable!();
                };
                anyhow::bail!("Zed cannot determine how to run this debug scenario. `build` field was not provided and Debug Adapter won't accept provided configuration because: {e}");
            };

            Ok(DebugTaskDefinition {
                label,
                adapter: DebugAdapterName(adapter),
                config,
                tcp_connection,
            })

View on GitHub (pinned to f4178619ac)

Solutions

1. Correct the adapter name in the task/scenario to a registered one (e.g. 'lldb', 'python')
2. Install or enable the extension providing that adapter

When it happens

Trigger: Thrown at crates/debugger_ui/src/session/running.rs:1260 when the library encounters an invalid state.

Common situations: See trigger scenarios.

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