动察 Beating AI News Flash: AI Agents are writing code faster and faster, but code review has become the new bottleneck.
In the past, a Pull Request typically represented hours or even days of a developer's work. Now an Agent can modify dozens of files at once, but what reviewers ultimately see is often just one massive code diff, making it hard to know under what requirements these changes were produced and what attempts were made along the way.
Zed's newly opened public beta Delta aims to restore this part of the process. It places Agent conversations, every code change, and subsequent comments into the same history. When you see a problematic piece of code, you can trace directly backward to see what requirements were proposed at the time and how the Agent gradually changed things to reach this point.
Review no longer has to wait until development is finished. Developers can open a separate thread at any time, have a person or another Agent inspect the current code, and continue making changes in an independent copy.
Zed has already tried it on itself first. The Delta repository has disabled GitHub Pull Requests, and 33 members have already merged 570 changes into the main branch through Delta.
Git is still retained, and commit, push, and build workflows are all unaffected. What Zed really wants to change is the code review layer: as more and more code is generated by Agents, looking only at the final diff may no longer be enough.
Delta currently supports macOS, Linux, Windows, and the web, and is free during the public beta. Features such as MCP and remote runtime environments are still in development.

