---
type: analysis
slug: research-zed-shipped-delta-as-a-separate-agent-review-product-now-in-public-beta
title: "Zed shipped Delta as a separate agent-review product, now in public beta"
description: "Zed opened Delta's private beta on August 12, 2026 and a public beta on September 16. Official blogs and docs now describe DeltaDB, Git-compatible CRDT sync, review threads, Cloudflare-backed storage, and shared Zed billing."
published_at: 2026-10-26T14:00:00.000Z
topics: ["github","agents","cli","research"]
source_urls: ["https://zed.dev/blog/introducing-delta","https://zed.dev/blog/introducing-deltadb","https://zed.dev/blog/delta-public-beta","https://delta.dev/","https://zed.dev/","https://delta.dev/deltadb","https://delta.dev/blog/future-of-version-control","https://delta.dev/docs/concepts/delta-and-git","https://delta.dev/docs/agents/review-and-sync","https://delta.dev/docs/privacy-and-security/data-storage","https://delta.dev/docs/privacy-and-security/security","https://delta.dev/download","https://delta.dev/roadmap","https://delta.dev/pricing","https://delta.dev/docs/account/plans-and-pricing","https://www.cameron.stream/3muicqu4nzk2a","https://tomrochette.com/agents/surfaces/delta/","https://newruntime.com/signals/zed-shows-agent-build-and-review-flow-in-delta-b68428/","https://newruntime.com/posts/developers-built-google-docs-and-figma-so-others-78a17f/"]
author: "Andrey Reshetnikov"
author_profile: https://newruntime.com/owner-profile.md
---
The flagged story was Zed's August 2026 private-beta launch of Delta, first seen as an X thread. The question was whether a real product sat behind that thread. It does. On August 12 Nathan Sobo introduced Delta as a multiplayer environment for coding with agents and reviewing what they build. It runs on DeltaDB, previewed June 11 as version control for work between Git commits. On September 16 Zed opened a public beta for macOS, Linux, Windows, and the web.

This matters because agent-generated diffs strain snapshot pull requests. Delta's bet is that conversation and worktree should be one replicated artifact, so a teammate or later agent can inspect intent instead of reconstructing it from a commit. That also puts uncommitted code and transcripts on vendor servers and treats the thread, not the pull request, as the unit of work.

## What we checked

- **Is there a Zed blog or docs page explaining DeltaDB, beta scope, and release availability beyond the X thread?** confirmed. Yes. Nathan Sobo's August 12, 2026 post introduced the private beta; a June 11 post defined DeltaDB; a September 16 post opened the public beta. Delta.dev now hosts the product, docs, download, roadmap, and pricing pages. [1][2][3][4][12][13]
- **Has New Runtime already covered Delta or DeltaDB?** partly confirmed. New Runtime later published a public-beta signal on agent build-and-review flow and an analysis of the October 15 DeltaDB CRDT post. I found no New Runtime item covering the original August 12 private-beta launch itself. [18][19]
- **Is Delta a separate application from the Zed editor rather than a feature inside it?** confirmed. Zed's homepage lists Delta (est. 2026) beside the editor (est. 2021). The August 12 post says DeltaDB could later come to Zed, but the first client is a new conversation-centered app. Downloads are at delta.dev, not as a Zed plugin. [5][1][12]
- **Does DeltaDB keep Git as the checkpoint while replicating uncommitted code and conversation onto Zed-operated servers?** confirmed. Docs say DeltaDB records edits, messages, and comments as deltas between Git commits; ignored files stay local. The same docs store Git objects and thread deltas on Cloudflare R2, Durable Objects, KV, and D1, and state that Delete Locally does not remove server copies. [8][10][6][7]

## What we found

- Zed published full product posts, not only a social thread. Introducing Delta (August 12, 2026) described private-beta invites, real-time worktree replication, in-thread review, a Rust-to-WebAssembly web client, cloud runners, and Claude Code as the first third-party harness. Software Is Made Between Commits (June 11) defined DeltaDB as operation-level version control with conflict-free replicated worktrees. Replace PRs with Delta (September 16) opened the public beta, said Delta is free during that beta, and promised paid plans plus a remaining free version. Product, docs, download, roadmap, and pricing pages now live at delta.dev. [1][2][3][4]
- Delta is a new application, not a Zed pane. Zed's homepage lists Delta beside the open-source editor. The August 12 post says adding DeltaDB to Zed would have constrained the database and disrupted existing users, so the first client is a new app with the conversation at the center. DeltaDB records each edit, message, comment, and file-tree change as a delta with a stable identity, loosely based on diamond-types CRDTs and adapted to Git. Commits, branches, and remotes stay in Git; teammates who never open Delta still see a normal repository. [5][1][6][7][8]
- Review is built around threads rather than pull-request snapshots. Docs describe isolated Delta worktrees, a Changes tab comparing against upstream, last commit, or last agent turn, and review subthreads with their own copies of parent worktrees. Reviewers comment on transcript or code, submit Approve or Request Changes, and can pull review edits back. Landing runs as a desktop Land subthread; agents can still push to a local remote or open a GitHub pull request. Zed says it disabled pull requests on Delta's own repository and that 33 people landed 570 changes to main after that switch; zed-industries/zed remains on GitHub. [9][3]
- DeltaDB is not local-only collaboration. Adding a repository stores Git objects and thread deltas on Zed's servers as well as on the machine, on Cloudflare (R2 for files and commits, Durable Objects for active deltas and settings, KV and D1 for metadata). Threads stay private until shared, but sharing grants access to attached repositories, including other Delta worktree histories for those repos. Delete Locally does not reliably remove server copies; account deletion is by email to privacy@zed.dev. Security docs describe TLS in transit, Cloudflare-managed encryption at rest, and local secret redaction before sync or model-provider calls. Untracked ignored files such as .env stay on the creating machine; tracked files that later match .gitignore are still imported. [10][11][8]
- Availability and pricing are public. The download page lists macOS, Linux, Windows, and the web. The roadmap marks Delta as in public beta, with repository-based GitHub access, a remote runtime, CLI, MCP, @mentions, and ACP in progress. Cloud Runners remain private beta. Pricing lists Personal at $0 (bring-your-own keys or external agents) and Pro at $10 per month with $5 of hosted tokens, on the same Zed account. Independent tester Cameron (September 1) praised commenting and speed but was unconvinced DeltaDB beat ordinary worktrees. Tom Rochette's October briefing called the revertible thread the durable idea and flagged server-side storage, closed-source DeltaDB, and the lack of remote merge gating. [12][13][14][15][16][17]

## What it means

Treat Delta as a thread-first collaboration product that sits beside Git, not as an optional pane in Zed. If you evaluate it, decide first whether uncommitted code, agent transcripts, and Git objects may live on Zed's Cloudflare backend; that is how sharing and multi-device sync work, and local delete does not retract server copies. Keep your source remote as the publish path. Landing is still an agent skill plus optional GitHub pull requests, not a remote-enforced gate, so regulated teams should not assume pull-request replacement is complete.

If you are building a competing agent environment, the transferable design is one history for conversation and edits, comments anchored to deltas rather than line numbers, isolated review worktrees, and Git as the checkpoint. The roadmap's ACP, MCP, and CLI items are the interoperability tests. Do not wait for DeltaDB inside Zed; the company said that is later, and the first client is this new app.

## Still open

- When, if ever, DeltaDB will be open-sourced or shipped inside the Zed editor.
- Whether in-progress repository-based GitHub permissions will replace invite-link sharing as the access model.
- Independent measurements of CRDT merge, large-repository performance, and concurrent-edit reliability.
- How Cloud Runners will be hosted; docs still mark provider, region, and paused-sandbox retention as TODO.

## Sources

1. [Introducing Delta — Zed's Blog](https://zed.dev/blog/introducing-delta) (primary)
2. [Software Is Made Between Commits — Zed's Blog](https://zed.dev/blog/introducing-deltadb) (primary)
3. [Replace PRs with Delta – Now in Public Beta — Zed's Blog](https://zed.dev/blog/delta-public-beta) (primary)
4. [Delta — A Multiplayer Environment for Coding with Agents](https://delta.dev/) (primary)
5. [Zed — Your last next editor](https://zed.dev/) (primary)
6. [DeltaDB — Keep the context behind every change](https://delta.dev/deltadb) (primary)
7. [DeltaDB: The Future of Version Control — Delta Blog](https://delta.dev/blog/future-of-version-control) (primary)
8. [Delta & Git — Delta Docs](https://delta.dev/docs/concepts/delta-and-git) (primary)
9. [Reviewing & Syncing Changes — Delta Docs](https://delta.dev/docs/agents/review-and-sync) (primary)
10. [Data Storage & Deletion — Delta Docs](https://delta.dev/docs/privacy-and-security/data-storage) (primary)
11. [Security — Delta Docs](https://delta.dev/docs/privacy-and-security/security) (primary)
12. [Delta — Download](https://delta.dev/download) (primary)
13. [Delta — Roadmap](https://delta.dev/roadmap) (primary)
14. [Delta — Pricing](https://delta.dev/pricing) (primary)
15. [Plans & Usage — Delta Docs](https://delta.dev/docs/account/plans-and-pricing) (primary)
16. [www.cameron.stream](https://www.cameron.stream/3muicqu4nzk2a)
17. [tomrochette.com](https://tomrochette.com/agents/surfaces/delta/)
18. [newruntime.com](https://newruntime.com/signals/zed-shows-agent-build-and-review-flow-in-delta-b68428/)
19. [newruntime.com](https://newruntime.com/posts/developers-built-google-docs-and-figma-so-others-78a17f/)

Author: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Github](https://newruntime.com/topics/github.md): Explore the github topic hub.
- topic hub: [Agents](https://newruntime.com/topics/agents.md): Explore the agents topic hub.
- topic hub: [Cli](https://newruntime.com/topics/cli.md): Explore the cli topic hub.
- collection: [Analysis](https://newruntime.com/analysis.json): Open the latest authorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)