zed-industries/zed · error

Failed to resolve context server

Error message

Failed to resolve context server

What it means

The modal could not determine how to run/configure the context server: both the extension-based resolution and settings-based resolution produced nothing, so the server cannot be resolved to an installable/configurable target.

Source

Thrown at crates/agent_ui/src/agent_configuration/configure_context_server_modal.rs:528

                    match workspace
                        .update(cx, |workspace, cx| {
                            resolve_context_server_extension(
                                server_id,
                                workspace.project().read(cx).worktree_store(),
                                cx,
                            )
                        })
                        .ok()
                    {
                        Some(task) => task.await,
                        None => None,
                    }
                }
            };

            match target {
                Some(target) => Self::show_modal(target, language_registry, workspace, cx).await,
                None => Err(anyhow::anyhow!("Failed to resolve context server")),
            }
        })
    }

    fn show_modal(
        target: ConfigurationTarget,
        language_registry: Arc<LanguageRegistry>,
        workspace: WeakEntity<Workspace>,
        cx: &mut AsyncWindowContext,
    ) -> Task<Result<()>> {
        cx.spawn(async move |cx| {
            let jsonc_language = language_registry.language_for_name("jsonc").await.ok();
            workspace.update_in(cx, |workspace, window, cx| {
                let workspace_handle = cx.weak_entity();
                let context_server_store = workspace.project().read(cx).context_server_store();
                workspace.toggle_modal(window, cx, |window, cx| Self {
                    context_server_store: context_server_store.clone(),
                    workspace: workspace_handle,

View on GitHub (pinned to f4178619ac)

Solutions

  1. Ensure the extension providing the context server is installed and up to date
  2. Restart the workspace so extension-based context servers can resolve
  3. Verify the server id matches a context server registered in settings or by an extension
Defensive patterns

Strategy: fallback

When it happens

Trigger: Thrown at crates/agent_ui/src/agent_configuration/configure_context_server_modal.rs:528 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/41da30e5862a08ec. Report an issue: GitHub.