Most challengers to GitHub promise a better version of the same workflow. Zed is arguing the workflow itself expired, and has put Delta into public beta to prove it — an environment where developers and coding agents share one live thread in place of the pull request. The claim carries more weight than most because Zed has already eaten the cost: pull requests are switched off on Delta's own repository, and 33 staff have landed 570 changes to main without them.
Key takeaways
- Delta runs on DeltaDB, which keeps the edits and the human-and-agent conversation that happen between Git commits — material Git ordinarily discards — while the commit stays the checkpoint teams push and build from.
- A reviewer joins the thread instead of reading a diff, inherits the original agent's context, and gets an isolated copy of the parent worktrees to run and change code without disturbing the author.
- The beta is free and runs on macOS, Linux, Windows and the web, with thread access from a mobile browser; paid tiers are promised but unpriced.
The diagnosis: review lost its context, not its scale
Pull requests are roughly 15 years old and encode an assumption that is quietly breaking — that whoever wrote the diff can explain it. Once AI agents produce most of the lines, volume grows while the reasoning stays locked in a session the reviewer never saw.
Zed is pointed about the usual mitigations. Stacking a large change across branches makes it easier to page through without restoring any of the thinking, and pasting a diff into a second agent asks that agent to reconstruct decisions the author already settled. Both treat legibility as a formatting problem. Zed's framing — why should a teammate's agent have to guess how you got there — locates it instead in what the tooling throws away at commit time.
What changes in practice
The practical shift is that collaboration stops waiting on push. Teammates are invited into an in-progress conversation with an agent, see the same worktrees, and work from their own machines; because the agent's context travels with the thread, a reviewer can ask it directly why the author chose a Mutex over an RwLock. Work survives the author logging off, and reviews can be split into subthreads whose isolated worktree copies let a reviewer fix a problem rather than merely flag it, folding the result back before the change lands.
That last capability is the genuinely novel one, and also where the open questions sit. A review in which the reviewer edits the code blurs the separation that made review an independent check, and teams with audit or compliance obligations will want to know how authorship and approval are attributed inside a thread. Zed has not detailed that yet.
Adoption is deliberately partial
Nothing here demands an all-or-nothing migration, and Zed is modelling the halfway state itself: zed-industries/zed stays on GitHub, where its community files issues, with contributors encouraged to share Delta threads alongside their pull requests. Since DeltaDB extends Git rather than displacing it, colleagues who never install Delta still see an ordinary repository — which is what makes a trial cheap to abandon, and is probably the most important design decision in the product.
The roadmap is more ambitious than the beta. Zed calls the target workflow continuous engineering, on the reasoning that integration and delivery went continuous while the rest of engineering stayed batched, and plans to move Git storage into DeltaDB and eventually pull CI-style verification into the thread through content-based builds. Today an agent can only trigger an existing CI provider and read the result before landing.
Outlook
Reading agent-written code as grounds to rebuild the forge is not a lone position — Cursor aimed Origin at GitHub's core workflows from a similar premise. What separates Zed is the bet underneath: rivals keep branches, commits and diffs as the primitives, while Zed expects the thread to become the unit of software development and deltas the right way to model its state. The commercial terms will decide how far the argument travels, and they are still unannounced beyond a promise that some free tier survives.
FAQ
Does Delta replace Git?
No. DeltaDB layers incremental, delta-based versions on top of Git's content-based versioning, and the commit remains what you push, pull and build from. The addition is the work between commits, which Git does not retain.
Is Delta free to use?
Yes, for the duration of the public beta. Zed says paid plans for individuals and teams are coming and that a free version will always exist, but has not published prices or explained what the free tier will include.
Can a team adopt Delta without leaving GitHub?
Yes, and Zed runs exactly that arrangement on its own open-source repository. Contributors share Delta threads next to their pull requests, while anyone who never opens Delta continues to work against a standard Git repository.
