zed-industries/zed · error

remote worktrees can't yet load binary files

Error message

remote worktrees can't yet load binary files

What it means

Returned by Worktree::load_binary_file when the worktree is the Remote variant. Binary file loading over a remote connection is not implemented yet, so the task fails immediately with this capability-gap sentinel.

Source

Thrown at crates/worktree/src/worktree.rs:939

    pub fn load_file(&self, path: &RelPath, cx: &Context<Worktree>) -> Task<Result<LoadedFile>> {
        match self {
            Worktree::Local(this) => this.load_file(path, cx),
            Worktree::Remote(_) => {
                Task::ready(Err(anyhow!("remote worktrees can't yet load files")))
            }
        }
    }

    pub fn load_binary_file(
        &self,
        path: &RelPath,
        cx: &Context<Worktree>,
    ) -> Task<Result<LoadedBinaryFile>> {
        match self {
            Worktree::Local(this) => this.load_binary_file(path, cx),
            Worktree::Remote(_) => {
                Task::ready(Err(anyhow!("remote worktrees can't yet load binary files")))
            }
        }
    }

    pub fn write_file(
        &self,
        path: Arc<RelPath>,
        text: Rope,
        line_ending: LineEnding,
        encoding: &'static Encoding,
        has_bom: bool,
        cx: &Context<Worktree>,
    ) -> Task<Result<Arc<File>>> {
        match self {
            Worktree::Local(this) => {
                this.write_file(path, text, line_ending, encoding, has_bom, cx)
            }
            Worktree::Remote(_) => {

View on GitHub (pinned to 9d272b0363)

Solutions

  1. Access the binary file from the local machine
Defensive patterns

Strategy: validation

When it happens

Trigger: Thrown at crates/worktree/src/worktree.rs:933 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/9af30488f851fb66. Report an issue: GitHub.