Zed opens Delta public beta for agent-led code review

• Delta is in free public beta for macOS, Linux, Windows, and the web, as zeddotdev's launch post announced; downloads are at Delta's site.
• Zed has already removed GitHub pull requests from Delta's own repository: zeddotdev's change table records 570 changes made without a PR, from 33 submitters.
• DeltaDB records the edits and human or agent messages between Git commits, zeddotdev's DeltaDB post says, while leaving commits as Git-compatible build and sharing checkpoints.
• Review happens in an isolated copy of a thread's worktrees, where reviewers can run agents and return fixes to the parent, according to zeddotdev's review post.

The official announcement says a mobile browser can follow active threads, and an agent can trigger an existing CI provider before landing. Richard Feldman's Delta walkthrough follows an issue fix through teammate review and merge. Zed's roadmap puts repository-based access, code-to-conversation navigation, and subagent side chats in the public-beta workstream.

Delta makes the thread, rather than a branch or pull request, the place where an idea, agent interaction, code, review, and landing accumulate. zeddotdev's launch post says each change stays linked to the conversation that produced it.

The announcement describes three mechanics:

• A teammate joins the existing agent conversation and sees the same worktrees on their own machine.
• The teammate can ask the original agent about prior implementation choices, including its Mutex versus RwLock reasoning.
• If the original author leaves, another person can continue the thread with that agent context.

A review is a dedicated subthread with the parent thread's agent context and an isolated copy of its worktrees. zeddotdev's review post says Delta generates guided reviews and keeps reviewer comments beside the people and agents that made the change.

The review flow in the public-beta post has three outcomes:

1. A reviewer asks for a revision in the parent thread.
2. A reviewer uses an agent to investigate or change code in the isolated copy.
3. The resulting fix is incorporated into the parent before the change is landed.

The isolation permits review experiments without altering the worktree that produced the original change.

DeltaDB extends Git's content-addressed versioning with incremental delta versions. zeddotdev's DeltaDB post says it keeps every edit between commits, plus the comments and conversations that shaped those edits.

The announcement separates two layers of history:

• Git commits: checkpoints for pushing, pulling, and building.
• DeltaDB versions: intermediate code evolution inside a thread, paired with human and agent messages.

Zed says this is compatible with a repository remaining on GitHub. Its own zed-industries/zed repository will continue to accept community pull requests, while contributors can attach Delta threads and collaborators who never open Delta still receive normal Git history.

Zed's table shows the cutover sharply: 43 of 59 changes arrived via PR on September 3, then 570 of 614 total changes across the displayed period arrived without one. zeddotdev's change table also lists 99 non-PR changes on September 15, with 25 unique submitters.

After guided review, the agent sequence in zeddotdev's /land post is:

1. Squash the work into one commit.
2. Push a branch and run CI.
3. Land on main after CI passes and a human approves.
4. Delete the branch and clean up.