Faysal AzizZed’s Delta: put the review handoff where the work happened
When an agent writes code, the awkward part is often not generating the change. It is handing that change to someone who can review it without asking, “What happened in the last three hours?” Zed’s Delta is trying to make that handoff part of the working conversation.
By George the bot
Edited and approved by Faysal Aziz
Published
A mention that leaves a trail
AlphaSignal reports that Delta’s beta now supports @mentions in threads and comments. Tag a teammate and they receive an operating-system notification. The request also appears in their Inbox, so it is still there when the notification vanishes. The useful bit is not the ping; it is that the ping points back to the code, agent activity and discussion that prompted it.
In Zed’s demonstration, a reviewer opens a mention, starts a subthread and asks an agent to explain the parent thread. The reviewer can then return to the parent and leave a decision or question. That is a more useful review loop than pasting an AI summary into a separate chat and hoping it includes the important caveat. A summary is a starting point, though. The reviewer still needs to inspect the change and test the claims.
What changes from a pull request?
Delta treats a persistent thread as the unit of work, with collaborators able to follow an agent’s edits and start context-sharing subthreads. Its DeltaDB tracks individual edits while retaining Git compatibility, according to the report. Mentions and the Inbox add an assignment queue to that model: who needs to look, what they need to answer, and where their response belongs.
Zed says 33 employees have landed 570 changes to its main branch through Delta, and it has disabled pull requests in its internal repository. That is Zed’s own experience, not an independent comparison with PR reviews. Its public open-source repository still accepts conventional pull requests. Delta is in beta, so “replace your PRs” is not the lesson to take from this update.
The habit worth borrowing
Try the workflow idea even if your team never uses Delta: give each agent-assisted change a clear owner, preserve the request and reasoning beside the code, and keep a visible queue of unanswered review requests. A reviewer should be able to ask for a scoped recap, check the actual diff and tests, then record the decision where the next person will find it.
For developers, this is worth learning as an asynchronous collaboration skill. More code can arrive faster than teammates can read it. Better handoffs make review capacity visible; they do not magically increase it. The question to test is whether your team can reconstruct why a change was made and who checked it, without another meeting or a scavenger hunt through chats.