Zed's Delta bets that git commits are the wrong unit for agent work
Zed opened the private beta for Delta yesterday, and the idea underneath it is sharper than the announcement. Delta is a multiplayer environment for coding with agents and reviewing what they build. It runs on DeltaDB, the replicated database Zed put on a waitlist back in June, which stores development as a continuous stream of edits rather than a sequence of commits.
Why that matters: a commit is a summary written after the fact. When a human wrote the code, the summary was mostly enough, because the reasoning lived in a head you could go ask. When an agent wrote the code across forty tool calls at two in the morning, the commit is a lossy compression of a conversation nobody kept. Reviewing it means reconstructing intent from a diff. DeltaDB captures every edit and every conversation between your commits, and stays compatible with git.
The features follow from that. Comments anchor to specific lines and survive as the code moves under them. Developers and agents share the same threads rather than the agent living in a side panel. Every participant holds a local copy synced in real time. It connects to Claude Code and other third-party agents, so Zed is not trying to own the model layer. And the whole thing compiles to WebAssembly and runs in a browser with nothing installed.
Zed calls this the second half of a plan years in the making: build the best place to write code, then make it the best place to talk about code. That is a polite way of saying they are coming for the pull request. GitHub's review surface was designed for humans reviewing humans at human volume. Nobody has yet built the review surface for the case where machines write most of it and one person has to say yes.
Private beta invites started going out yesterday. https://zed.dev/blog/introducing-delta
← Back to all articles
Why that matters: a commit is a summary written after the fact. When a human wrote the code, the summary was mostly enough, because the reasoning lived in a head you could go ask. When an agent wrote the code across forty tool calls at two in the morning, the commit is a lossy compression of a conversation nobody kept. Reviewing it means reconstructing intent from a diff. DeltaDB captures every edit and every conversation between your commits, and stays compatible with git.
The features follow from that. Comments anchor to specific lines and survive as the code moves under them. Developers and agents share the same threads rather than the agent living in a side panel. Every participant holds a local copy synced in real time. It connects to Claude Code and other third-party agents, so Zed is not trying to own the model layer. And the whole thing compiles to WebAssembly and runs in a browser with nothing installed.
Zed calls this the second half of a plan years in the making: build the best place to write code, then make it the best place to talk about code. That is a polite way of saying they are coming for the pull request. GitHub's review surface was designed for humans reviewing humans at human volume. Nobody has yet built the review surface for the case where machines write most of it and one person has to say yes.
Private beta invites started going out yesterday. https://zed.dev/blog/introducing-delta
Comments