Replace PRs with Delta – Now in Public Beta — Zed's BlogProductResourcesExtensionsDocsPricingDeltaPSign upSDownloadDReplace PRs with Delta – Now in Public BetaNathan SoboSeptember 16th, 2026On This PageCode review without pull requestsBuilt on DeltaDB, compatible with GitFollow our quest to replace GitHub.comTry the public betaWhat's next for Zed?See our roadmap →Today, we're launching the public beta of Delta, a multiplayer environment for coding with agents and reviewing what they build. We're building Delta because agents have fundamentally changed the way we write software, but our collaborative tooling isn't keeping up.
Last week, we crossed a key milestone: we disabled pull requests on Delta's own repository. We now build and collaborate on Delta entirely within Delta.
Pull Requests are seriously turned off.
What makes Delta different from traditional workflows is that collaboration doesn't depend on committing and pushing code. You invite teammates directly into your conversations with agents. When someone joins your thread, they see the same worktrees you do and can work with them on their own machine. Teammates can ask the same agent why you chose a Mutex instead of an RwLock. If you log off, they can keep working with the agent where you left off.
Starting today, anyone can download Delta for macOS, Linux, or Windows, use it on the web without downloading anything, and keep up with threads from a mobile browser on the go.
Richard Feldman walks through an end-to-end flow in Delta: fixing an issue, getting a teammate's review, and merging it.
Code review without pull requests
Since GitHub introduced pull requests over 15 years ago, they've become the standard way to ask teammates to review changes to your codebase. But with agents generating so much code, the diffs we're asking each other to review have mushroomed.
Splitting a big diff across a stack of branches can make it easier to navigate, but the decisions behind the code still need review. Smaller diffs don't supply that context. A reviewer may feed your diff into another agent to help understand it, but that agent has to piece together decisions you already worked through.
Why should your teammate's agent have to guess how you got there?
In Delta, you can invite anyone to pick up a thread where you left off, or create a dedicated review subthread. A review guides you through your branch's changes with access to the original agent's context. Each review gets its own isolated copy of the parent thread's worktrees, so you and your teammates can use agents to explore the code and try changes without disrupting the original work. If a reviewer spots a problem, they can request a revision or work with an agent to fix it themselves. Fixes made during review can be incorporated into the parent thread before you ask the agent to land the change.
A short walkthrough of making a change and getting reviews, in Delta.
Built on DeltaDB, compatible with Git
Delta is built on DeltaDB, which extends Git's content-based versioning with incremental versions based on deltas. It records edits between commits alongside messages from humans and agents, preserving how the code evolved throughout a thread. A commit remains the checkpoint you push, pull, and build from. DeltaDB retains the work between those checkpoints.
You don't have to move your whole team into Delta to use it.
For example, zed-industries/zed will remain on GitHub for now because it's where our community finds issues and submits changes. We're encouraging Zed contributors to share Delta threads alongside their pull requests. Contributors can work together in Delta while continuing to submit changes through GitHub, and teammates who never open Delta still see a normal Git repository.
Follow our quest to replace GitHub.com
It seems like everyone is in a race to replace GitHub right now. Most contenders promise better uptime on top of the same old primitives: branches, commits, and diffs.
We believe that threads will be the new fundamental unit of software development, and the best way to model their state is with deltas.
Pull requests are the first part of the GitHub workflow we're leaving behind. In their place is the Delta thread, and with it a way of working we call continuous engineering. The industry made integration continuous, then delivery, while the rest of software engineering still happened in batches. In a Delta thread, the idea, implementation, review, and landing of the changes can all happen in the same place.
We're building better alternatives for the other workflows that bring developers to GitHub.com, starting with Git storage in DeltaDB. Longer term, content-based builds could bring CI-style verification directly into the thread. For now, an agent can trigger a run with an existing CI provider and check the results before landing the change.
Try the public beta
Thank you to the thousands of people who requested early access and helped us find Delta's rough edges. Delta is forming, and some of the capabilities we care most about are ahead (follow what we're building next here). But it's already our daily driver: 33 of us have landed 570 changes to main since we turned off pull requests.
During the public beta, Delta is free. We'll introduce paid plans soon for individuals and teams. There will always be a free version of Delta.
Download Delta, kick off an agent, invite a teammate into the thread, and feel the magic. We'd love to hear how it goes.Related PostsCheck out similar blogs from the Zed team.The Case for Software Craftsmanship in the Era of Vibes|Agentic Engineering|Jun 12, 2025Building a platform that open sources itselfJun 14, 2023We're Not Building AI Features for the Money|Featured|May 05, 2026Looking for a better editor?
You can try Zed today on macOS, Windows, or Linux. Download now!We are hiring!
If you're passionate about the topics we cover on our blog, please consider joining our team to help us ship the future of software development.Zed Industries © 2026Sign Up · Have an account? Sign InTerms of Service · AttributionsManage Site CookiesProductDownloadPricingBusinessReleasesExtensionsRoadmapDocsCompareGitHub↗Status↗ResourcesFAQCLACommunitySupportDiscussions↗PrivacySubscribeTheme BuilderYearly RecapsCompanyBlogAboutValuesTeamJobsPressBrandMerch↗SocialTwitter↗Bluesky↗Instagram↗YouTube↗Discord↗Reddit↗

The launch of Delta marks a significant shift in software collaboration, fundamentally aiming to replace the traditional pull request workflow by introducing a system based on collaborative threads facilitated by agents. This initiative is driven by the observation that the rise of software agents has altered the way code is written, creating a need for a more dynamic and contextual collaboration tool than current methods provide. Delta centers on the concept that the idea, implementation, review, and final landing of changes should occur within a single continuous thread, thereby embodying a philosophy of continuous engineering.

The core differentiation of Delta from conventional workflows, such as those on GitHub, lies in decoupling collaboration from the necessity of committing and pushing code. Instead of relying on branching to separate work, Delta invites teammates directly into the ongoing discussions with agents. When a teammate joins a thread, they gain access to the same worktrees as the original developer and can interact with agents to explore code or suggest changes. This allows for contextual collaboration, where users can ask agents for justifications regarding specific coding decisions, such as why a Mutex was selected over an RwLock, without needing to piece together context from separate diffs.

A key mechanism Delta employs for handling reviews is the provision of isolated worktrees. Each review or thread is given an independent copy of the parent thread's worktrees, ensuring that reviewers can explore proposed changes and engage with agents to test revisions without disrupting the primary development line. This isolation enables reviewers to request specific revisions or work with agents to implement fixes that can be incorporated into the parent thread before finalizing the change.

Technically, Delta is built upon DeltaDB, which extends Git's foundational capabilities by implementing content-based versioning using incremental deltas. DeltaDB records all edits between commits, along with accompanying messages from both human developers and automated agents, thereby preserving the complete evolution of the code throughout a collaboration thread. A commit remains the definitive checkpoint from which work can be pulled and built, while DeltaDB retains all the transitional work that occurred between those checkpoints.

Furthermore, Delta facilitates a relationship with existing systems rather than demanding complete migration. The development team acknowledges that community activities, such as issue reporting and change submission, will continue on platforms like GitHub. Contributors can leverage Delta threads for their collaborative agent work while still utilizing existing repositories for submission. This approach allows users to adopt the novel thread-based methodology gradually.

The vision extends beyond the immediate workflow changes; Delta seeks to establish collaborative threads as the new fundamental unit of software development. This trajectory implies a future where continuous engineering—encompassing the initial idea, agent-driven implementation, peer review, and deployment—is seamlessly integrated into a unified environment. While the current public beta offers access to these novel capabilities, the project is evolving toward broader integration, including exploring content-based builds for verification and considering how agents can interface with continuous integration providers to validate changes before they are landed. Delta is currently in public beta, offering access to users on macOS, Linux, and Windows, and is intended to remain free during this phase before introducing paid tiers for individuals and teams.