Zed Delta puts agent code review in one shared thread

Your agent wrote 900 lines and a 40-turn transcript explaining why. The pull request shows you the 900 lines. The reasoning lives in someone's terminal scrollback, and by review time it's gone. Zed shipped a product aimed squarely at that gap: Delta, which the company calls a multiplayer environment for coding with agents and reviewing what they build. Agent code review is the bottleneck, and Delta's bet is that reviewing the conversation and the diff separately is the reason.

What actually happened

Per Zed's announcement on August 12, Delta is a standalone application built on DeltaDB, Zed's version control layer. DeltaDB is CRDT-based and records edit operations continuously rather than only at commit boundaries — so the history has the steps in it, not just the snapshots.

What that buys, per Zed:

• The worktree and the conversation replicate together, in real time, to everyone in the thread. A teammate joins and gets a synchronized local copy of the code.
• Teammates are first-class participants. They can comment, co-edit the prompt, or take over the work without anyone pushing a commit first.
• Comments stay anchored to the code they're about as the code keeps changing underneath them.
• Third-party agent harnesses plug in, starting with Claude Code — a session syncs live into a Delta thread.
• Work can move to cloud runners, and a thread can be shared by browser link with no install.

The part that matters for adoption: teammates who don't use Delta still see an ordinary git repository. Some coverage framed this as replacing git. Zed's own post doesn't — it describes working with existing repos.

Delta is in private beta. First invites went out on announcement day.

Why this matters for your business

You do not need Zed's product to take the point. The point is that agent output has two halves — the diff and the reasoning that produced it — and most teams have tooling for exactly one of them. Reviewers approve code without the transcript that explains the tradeoff, or they read a transcript detached from the code it changed.

Fix that with process before you buy anything. Require the agent transcript in the PR description. Log the prompt that produced the branch. Make "why did it choose this" answerable without a Slack archaeology dig. Every dollar you save generating code you spend validating it — which is why CI became an AI line item and why review, not writing, is now the constraint.

And note what Zed did right on the way out: normal git underneath. Adopt tools that degrade to a format you already own. Private beta products change or disappear. Your repo shouldn't.

Sources: Zed — Introducing Delta.