Zed launches Delta to move AI code review inside agent conversations

Zed CEO Nathan Sobo launched Delta on August 12th, opening a private beta for a multiplayer application that keeps agent conversations, code changes, and review comments in one synchronized workspace. Delta runs on DeltaDB, Zed's operation-level versioning system, and supports cloud runners and browser access, with Claude Code as its first third-party agent integration. The app is a separate product from the Zed editor, allowing Zed to test DeltaDB before integrating it into the editor.

Zed https://zed.dev/blog/introducing-delta CEO Nathan Sobo @nathansobo https://x.com/nathansobo launched Delta https://delta.dev/ on August 12th, opening a private beta for a multiplayer application that keeps agent conversations, code changes and review comments in one synchronized workspace. The first invitations went out alongside the announcement, with Zed planning to admit more users over the coming weeks. zed.dev https://zed.dev/blog/introducing-delta Delta extends a technical thread that Sobo and co-founders Antonio Scandurra @as cii https://x.com/as cii and Max Brunsfeld @maxbrunsfeld https://x.com/maxbrunsfeld have followed since their years building Atom at GitHub. Sobo led Atom until 2018 and co-led Teletype, an early production use of conflict-free replicated data types, or CRDTs, for collaborative editing. Scandurra also worked on Teletype, while Brunsfeld created the Tree-sitter parsing framework before co-founding Zed. zed.dev https://zed.dev/team That background explains Delta's design. Zed has spent years building collaboration into an editor. Delta puts the conversation at the center and treats the code, agent activity and human review as parts of the same persistent thread. Review follows the code as it changes Delta runs on DeltaDB https://zed.dev/blog/introducing-deltadb , Zed's operation-level versioning and synchronization system. DeltaDB records fine-grained edits between Git commits and replicates the conversation and worktree across participants. Each developer receives a local copy of the code that remains synchronized as humans and agents make changes. Existing Git repositories continue to work normally, including for collaborators who never open Delta. zed.dev https://zed.dev/blog/introducing-deltadb Traditional review comments are attached to a commit or other fixed snapshot. Delta instead lets developers comment on a line in the live worktree or on a specific passage in an agent transcript. Zed says DeltaDB anchors those references to individual operations, allowing a comment to follow the relevant code as surrounding lines move or change. Reviewers can ask the agent that produced a change to explain or revise it without reconstructing the original task from a diff. zed.dev https://zed.dev/blog/introducing-delta Delta also supports cloud runners, allowing an agent to continue working after a developer closes a laptop. Shared threads can open in a browser without installing the desktop application. Zed says the browser client is the same Rust application compiled to WebAssembly and rendered through WebGL. Delta's first third-party agent integration is Claude Code, whose terminal sessions can synchronize into a shared thread for teammates to watch, annotate or continue. zed.dev https://zed.dev/blog/introducing-delta Zed has also redesigned the chat interface around editing rather than message passing. Developers can move a cursor through an agent transcript and attach comments to a plan, reasoning block or diff instead of sending every correction through a text box at the bottom. Zed says Delta displays full transcripts and diffs rather than routinely collapsing or summarizing them. Those performance claims will face broader testing as access expands beyond the initial private beta. zed.dev https://zed.dev/blog/introducing-delta Delta becomes Zed's proving ground Delta is a separate application rather than a feature inside the Zed editor. That decision is the strategic core of the launch. Zed had originally planned to introduce DeltaDB through its existing editor, but Sobo wrote that rebuilding Zed's foundations around the replicated database would risk disrupting workflows used by what Zed describes as hundreds of thousands of daily users. Delta gives Zed a smaller surface on which to test the database and its thread-centric interface before bringing DeltaDB into the editor. zed.dev https://zed.dev/blog/introducing-delta The launch also puts last year's financing into context. Zed raised a $32M Series B https://zed.dev/blog/sequoia-backs-zed led by Sequoia Capital in August 2025, with existing investors participating. Zed said the round brought its total funding above $42M and would finance DeltaDB and a broader collaboration layer for developers and agents. The private beta is the first standalone product built around that investment thesis. zed.dev https://zed.dev/blog/sequoia-backs-zed?utm source=openai Delta positions Zed around a growing bottleneck in agentic development: reviewing and maintaining the volume of code that agents can produce. The application does not depend on Zed building the underlying model. Its value rests on preserving intent, edits and human feedback across whichever agents generate the code, beginning with Claude Code. Sobo summarized the product decision in the announcement: "the thread is where software happens now." Delta turns that thesis into a distinct application, while protecting Zed's established editor from an immediate architectural overhaul. Zed now has to prove that developers want another durable system alongside Git, and that operation-level history provides enough useful context to justify keeping every conversation tied to the code that followed. zed.dev https://zed.dev/blog/introducing-delta