Zed Delta Explained: Multiplayer Coding With AI Agents

- Delta, announced by Zed on August 12, 2026, is a multiplayer environment for coding with agents and reviewing what they build
- A CRDT-based layer called DeltaDB captures every edit and conversation between commits, replicating them to all thread participants in real time
- Delta does not replace git. You can still commit and push as usual, and to teammates not using Delta, the repo just looks like a normal git repository
- The first supported agent harness is Claude Code, connected via the open Agent Client Protocol (ACP), with terminal sessions live-synced into a Delta thread
- Delta is currently in private beta (invite-only), with invites rolling out gradually. Pricing has not been announced

Delta is a new environment announced on August 12, 2026 by Zed Industries, the team behind the Zed code editor. In its own words, Zed describes Delta as "a multiplayer environment for coding with agents and reviewing what they build." The core idea is that reviewing the code an agent wrote happens in the same place where the work actually happened. As more teams let AI agents write substantial amounts of code, tracking and discussing what an agent actually changed, and why, has often been an afterthought — Delta is positioned as an answer to that gap. For full details, see the official announcement at zed.dev/blog/introducing-delta.

At the core is DeltaDB, a CRDT (Conflict-free Replicated Data Type) based version control layer that captures every edit operation and conversation that happens between commits. This means teams get access to more than the final diff — they get the full process that led up to it, shared with everyone on the thread.

Delta is real-time and multiplayer by design. Teammates can join a thread without waiting for a commit or push, leave comments, co-edit prompts sent to the agent, and hand off in-progress work to another team member. Where traditional PR-based review happens after the work is done, Delta is built for watching and intervening in work while it's still in progress.

On the agent side, Delta connects to third-party agent harnesses, with Claude Code as the first one supported. The connection runs over the open Agent Client Protocol (ACP), so you can keep working with Claude Code in a terminal while that session is live-synced into a Delta thread. For more on getting the most out of Claude Code itself, see our complete guide to Claude Code.

There is also a browser version. Zed's Rust application is compiled to WebAssembly and rendered with WebGL, delivering the same experience as the desktop app without requiring an install. The core Zed editor itself runs on macOS, Windows, and Linux.

DeltaDB is built on CRDTs (Conflict-free Replicated Data Types), a data structure that lets multiple participants edit the same data concurrently without conflicts — the same class of technology that underlies collaborative editors like Google Docs. Delta uses this to capture the fine-grained edit operations (keystroke-level changes, files created or moved) and the conversations attached to them (instructions given to an agent, comments from teammates) that occur between one commit and the next. In plain git, history only exists at the commit level, so all the back-and-forth that led to a given commit is normally lost. DeltaDB captures that missing layer of information and replicates it to every participant on the thread in real time.

It's worth being explicit here: Delta does not replace git. Developers using Delta can still commit and push exactly as before, and to a teammate who isn't using Delta, the repository looks like an ordinary git repository. In other words, Delta is a layer added on top of git that preserves the information git normally discards between commits, designed to coexist with existing git workflows, CI/CD pipelines, and GitHub-based PR review. That positioning sets it apart from tools like Hunk, a terminal diff viewer focused on commit-level diffs, or Graphite, which is built around stacked PRs.

As of August 17, 2026, Delta is in private beta and invite-only, with invites rolling out gradually. Pricing has not been disclosed as of the announcement, and it's currently unclear when or at what price general availability will arrive. If you're interested, checking the official announcement page for the current state of invites is the most reliable way to find out.

- Get an invite (Delta is invite-only during private beta, with invites rolling out gradually)
- Create a thread in Delta and invite your teammates
- Connect an agent harness — Claude Code is the first one supported — via the Agent Client Protocol
- Work as usual with Claude Code in a terminal; that session live-syncs into the Delta thread
- Teammates can join the thread before any commit or push, leaving comments, co-editing prompts, and handing off work

Note: the official announcement, as of August 17, 2026, does not lay out specific commands or a detailed step-by-step workflow.

Delta is often discussed alongside plain Git plus GitHub PRs, Graphite (built for stacked PRs), the terminal diff viewer Hunk, and Herdr, which multiplexes several agent sessions at once. To be clear about where Delta fits: it is not a git replacement — it's a layer that preserves the information git drops between commits, namely the edit operations and the conversations with agents.

Delta could be a strong fit for teams that are increasingly having agents (Claude Code in particular) write code, and want a real way to review that work together as a team. It's especially relevant if you want the team to see and discuss why an agent made a given change, or want teammates to be able to step in before anything is even committed. That said, as of August 17, 2026, Delta remains in private, invite-only beta, with no announced timeline or pricing for general availability — it's not something you can drop into production workflows today. It makes sense to keep an eye on invite availability and future announcements while continuing to rely on your existing git-plus-PR review workflow in the meantime. For related tooling, see our coverage of Mosaic, a tool for managing parallel Claude Code sessions, and our comparison of Claude Code, Codex, Cursor, and Copilot.