zed-industries/zed · error

no file found at path {abs_path:?}

Error message

no file found at path {abs_path:?}

What it means

Logged in open_abs_path_at_point when neither the project's find_project_path nor the subsequent filesystem lookup could locate a file at the given absolute path. The helper is used to open links and @-mentions from assistant messages; the offending input is abs_path from the link/mention URI, which points at a file that no longer exists or was never part of any worktree.

Source

Thrown at crates/agent_ui/src/agent_ui.rs:147

    window: &mut Window,
    cx: &mut Context<Workspace>,
) {
    let project_path = workspace
        .project()
        .update(cx, |project, cx| project.find_project_path(&abs_path, cx));
    let fs = workspace.project().read(cx).fs().clone();
    let workspace = cx.weak_entity();
    window
        .spawn(cx, async move |cx| {
            let item = if let Some(project_path) = project_path {
                workspace
                    .update_in(cx, |workspace, window, cx| {
                        workspace.open_path(project_path, None, true, window, cx)
                    })?
                    .await?
            } else {
                let metadata = fs.metadata(&abs_path).await?;
                anyhow::ensure!(
                    metadata.is_some_and(|metadata| !metadata.is_dir),
                    "no file found at path {abs_path:?}"
                );
                workspace
                    .update_in(cx, |workspace, window, cx| {
                        workspace.open_abs_path(
                            abs_path,
                            OpenOptions {
                                focus: Some(true),
                                ..Default::default()
                            },
                            window,
                            cx,
                        )
                    })?
                    .await?
            };
            let Some(point) = point else {

View on GitHub (pinned to 9d272b0363)

Solutions

1. Verify the file still exists on disk at the linked absolute path
2. Reopen the project or add the file's directory as a worktree so it is indexed
3. Regenerate the link or mention from the current file location

When it happens

Trigger: Thrown at crates/agent_ui/src/agent_ui.rs:147 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/f8cf0d357e8f5553. Report an issue: GitHub.