GoKawiilToday we're introducing Delta, 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, a multiplayer environment for coding with agents and reviewing what they build.
Delta is the second half of a plan we've been executing for years: to build the best place to write code, then make it the 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 built DeltaDB, 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 captured between your 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.
Picking up a thread from a teammate, adding some more comments, and moving forward with implementation.
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.
Adding comments directly in a diff and seeing them replicated in the thread.
... continue reading