← In the News

Zed built a new application around the idea that review belongs between commits

Introducing Delta · Nathan Sobo, Zed Industries · Zed Blog, August 12, 2026

Machine-readable Download Markdown

Delta is a separate application from Zed, in private beta as of yesterday, built on DeltaDB, the version control layer Zed has been developing publicly. The argument is about where the record of agent work lives. "On a commit-based platform, comments attach to snapshots and fall out of date as soon as the code changes." DeltaDB instead captures every edit and conversation between commits, replicating the worktree and the thread together, while leaving the underlying git repository intact: "teammates who never open Delta see a normal git repo."

The practical consequence Zed is aiming at is review. Comments anchor to lines in the evolving worktree rather than to a diff snapshot, the agent stays in the thread with the conversation that produced the code, and, in Sobo's framing, "you don't reconstruct intent from a diff. You ask the agent to explain it or fix it." The post is also blunt about interface load: "Agents produce more text and bigger changes than any human, and most tools cope by hiding things (e.g. collapsing diffs, truncating transcripts, summarizing what you should be able to read)." Delta renders diffs and transcripts in full and treats the conversation as a document you can put a cursor anywhere in. It connects to third-party agent harnesses, starting with Claude Code, so a terminal session syncs into a shared thread.

This is an announcement with a waitlist behind it, not something you can evaluate today. Invites went out on the 12th with more promised over the coming weeks.

Why it matters: If the argument holds, the reviewable artifact for agent-written code stops being the diff and becomes the conversation plus the operation stream that produced it. That is a claim about what a team should be keeping, and it is testable against your own practice now: for the last non-trivial change an agent made in your codebase, ask whether the commit contains enough to review it, or whether the reasoning you would need is in a chat window nobody archived.