Today we’re introducingDelta, a multiplayer environment for coding with agents and reviewing what they build, and we’re inviting the first users into our private beta. Delta keeps code and conversations connected, so developers and agents can work together with the full context of how the code came to be.
Delta is the second half of a planwe’ve been executing for years: to buildthe best place to write code, then make itthe best place to talk about code. When we first started out, not everyone understood why you’d want to have a conversation inside your IDE. Then came agents, and now talking about code is how software gets written.
To support our collaborative vision, we builtDeltaDB, which replicates the conversation and the worktree together, in real time, for everyone in a thread. DeltaDB works with the git repository you already have. Every edit and conversation is capturedbetweenyour commits. You can commit and push like you always did, and teammates who never open Delta see a normal git repo.
We could have added DeltaDB to Zed, and eventually we will. But the best possible experience required an entirely new kind of application. Building Zed made performance and craft an obsession for us, and Delta is built on those same principles.
On a commit-based platform, comments attach to snapshots and fall out of date as soon as the code changes. In Delta, you and your team can comment on anything: the conversation, or any line of code in the worktree, whether an agent touched it yesterday or a human wrote it three years ago. Everyone sees every comment in place, anchored to the code as it evolves, connected to the conversations that produced it.
And the agent is right there in the thread, working from the same original conversation and decisions as you. When something looks wrong, you don’t reconstruct intent from a diff. You ask the agent to explain it or fix it. Review stays connected to the conversation and code as both evolve.
Over time, that context helps future teammates and agents understand not only what the code does, but why it took its current shape. The history stays with the code in DeltaDB, and it surfaces right where it’s relevant.
DeltaDB makes the worktree itself collaborative. Every participant gets their own copy of the code on their local machine, kept in sync in real time as the work happens.
DeltaDB also brings multiplayer to the cloud. Move your work to a cloud runner, close your laptop, and the agent keeps going while its conversation and code stay synchronized with the thread.
Showing everything only matters if you can act on it. In most agent tools, the conversation is something you watch. Output streams past, and your only way to respond is the text box at the bottom. Reacting to three parts of a plan means three serial messages, or hoping the answers don’t tangle.
In Delta, the conversation is a document, and your cursor works everywhere in it. Move through the thread with the same keyboard motions you use on code. When you want to respond to something, put your cursor on it and start typing. Comments attach to the exact text they’re about, and nothing in the thread is off limits: a line of the diff, a step in the plan, a thinking block. The agent sees precisely what you mean, and so does everyone else.
Delta gives us a focused place to iterate quickly and improve the primitives through real product use. We’ll keep developing Zed, and DeltaDB will come to it, but Delta is where it begins.