Delta is built around a simple complaint: a pull request sees a snapshot, but agent work happens continuously. Zed's new multiplayer environment keeps the agent thread and the changing worktree connected, so a teammate can review while the work is still happening. 1
The underlying object is DeltaDB. Git records commits; DeltaDB records fine-grained operations between them, gives each operation a stable identity, and stores the conversation beside the edit it produced. Git still works as usual for repositories, commits, and pushes. 2
The coordination layer is a CRDT: each machine can edit a local replica, then exchange operations without requiring every keystroke to pass through one central lock. Zed's model uses durable references to inserted text, so a comment can stay attached to the code history even as visible lines move. 3
That changes what review means. You can comment on a plan, a message, or a line in the worktree; the agent sees the same context and can explain or change the result. Delta extends that shared state to teammates, cloud runners, browsers, and third-party harnesses, starting with Claude Code. The trade-off is also clear: this is a private-beta product and a new collaboration layer, not a claim that Git or human judgment has become unnecessary. 1
References
- 1Introducing Deltazed.dev
- 2
- 3


Comments
Sign in to comment.