Zed Turned Off Pull Requests

Zed did not ship a nicer pull request. They turned the pull request off.

On 16 September 2026 the company opened a public beta of Delta, a multiplayer workspace for coding with agents. Last week they disabled GitHub pull requests on Delta's own repository. Nathan Sobo, Zed's CEO, says they now build Delta inside Delta. That is not a slogan. It is the product test.

Image: Zed Industries, Replacing Pull Requests with Delta, 16 September 2026.

The thread, not the diff

A GitHub pull request is a batch. You commit, you push, you ask someone to look at a slice of history. That made sense when a person typed the code over a few hours. Agents dump a week of changes in a sitting. The reviewer gets a wall. They paste the wall into another agent. That second agent was not in the room when the first one made the choices, so it guesses.

Delta's unit is a thread. You invite a teammate into the same agent conversation. They see the same worktrees on their machine. They can ask the same agent why it picked a Mutex. If you log off, they keep going. Review is a subthread with its own copy of those worktrees, so a reviewer can poke the code without wrecking the original run. Accepted fixes fold back before anyone lands the change.

Git does not go away

Underneath sits DeltaDB. It records the edits between commits, plus the messages from humans and agents, so the conversation and the files stay tied together. A commit is still the checkpoint you push and build from. Teammates who never open Delta still see a normal Git repo.

Zed is not pretending the whole world will move tomorrow. The open-source Zed editor stays on GitHub because that is where issues and outside patches live. Contributors can share a Delta thread next to a pull request. The public repo still looks like a public repo.

What 570 merges actually prove

Zed says 33 people have landed 570 changes to main since they killed pull requests on that repo. Treat that as a vendor number from a small, fast team that already lives in its own editor. It is a useful stress test. It is not your org's merge queue.

The claim that matters is smaller: if agents write most of the code, the review object has to carry the reasoning, not just the diff. A stacked PR can slice the diff. It still drops the trail. A thread keeps both.

Sobo wrote that everyone is in a race to replace GitHub, and most of the racers are selling better uptime on the same primitives: branches, commits, diffs. Delta's bet is that the primitive should be the thread, and that CI still happens by asking an agent to kick your existing provider before landing.

The public beta is free on macOS, Linux, Windows, and the web. Paid plans are coming. There will still be a free version. Use it on work where you would have asked a teammate to sit next to the agent, not on a drive-by typo.

Sources

Zed Industries, Replacing Pull Requests with Delta, 16 September 2026. https://zed.dev/blog/delta-public-beta

Zed Industries, Introducing Delta, 12 August 2026. https://zed.dev/blog/introducing-delta

Paul Sawers, The New Stack, 16 September 2026. https://thenewstack.io/zed-delta-github-alternative/