zed-industries/zed · error

mapped {description} `{}` does not exist in {}

Error message

mapped {description} `{}` does not exist in {}

What it means

After translating a cwd/writable path into the WSL distro, the resolved path does not actually exist there (the plain existence check failed). A bad request: the granted path isn't present, so sandboxing cannot bind it.

Source

Thrown at crates/sandbox/src/windows_wsl.rs:1102

        .zip(resolved)
        .map(|((mapping, description, required), resolved)| {
            if resolved.used_fallback
                && let PathMapping::NativeDrive { windows_path, .. } = mapping
            {
                log::warn!(
                    "failed to translate `{windows_path}` with wslpath in {}; \
                     falling back to `{}`",
                    wsl_distro_label(distro),
                    resolved.path
                );
            }
            if !resolved.exists {
                // A bad request (the path simply isn't there), not an
                // environment problem — the model can create it or fix the path
                // and retry, so no `WSL_SANDBOX_UNAVAILABLE_PREFIX`. Protected
                // Git paths are allowed to be absent, matching Linux bwrap's
                // behavior: a missing path cannot be overlaid, so it is skipped.
                ensure!(
                    !required,
                    "mapped {description} `{}` does not exist in {}",
                    resolved.path,
                    wsl_distro_label(distro)
                );
                return Ok(None);
            }
            Ok(Some(resolved.path))
        })
        .collect()
}

/// Flatten path mappings into the `(kind, path, fallback)` argument triples
/// consumed by [`PATH_RESOLUTION_SCRIPT`].
fn path_resolution_args<'a>(mappings: impl Iterator<Item = &'a PathMapping>) -> Vec<String> {
    let mut args = Vec::new();
    for mapping in mappings {
        match mapping {

View on GitHub (pinned to f4178619ac)

Solutions

1. Verify the path exists inside the selected WSL distro (not just on the Windows side)
2. Correct typos or stale paths in the request before retrying
3. Ensure wslpath translation produced the intended Linux-side path

When it happens

Trigger: Thrown at crates/sandbox/src/windows_wsl.rs:1102 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/8b7edf9cff7ec37f. Report an issue: GitHub.