Post

I have never been a big fan of pull requests.

Before agents, it was easier to believe that the ceremony of trading comments on snapshots was an effective way to collaborate on software, but it never really worked for the Zed team. We frequently work together in the same worktree, building trust and shared understanding by discussing the code as we write it . GitHub doesn't let you talk about code until after you commit and push, but by then our most important conversations are usually already over.

So in 2021, we founded Zed to move beyond the constraints of commits. Our plan was to build an editor worthy of the world's best developers , then offer a better way to work together inside it. We didn't foresee then how the problems we'd spent years thinking about in the context of human-to-human collaboration would become even more important when collaborating with agents.

Increasingly, the conversation that generates the code is becoming the true source of our software. That conversation unfolds continuously and must be cross-referenced to the code as it changes. Git, organized around discrete commits, was never designed to support this.

So we're building something that is. We call it DeltaDB, a new kind of version control built on a single coherent abstraction that transforms your conversations with agents and the worktrees they edit into shared artifacts. We've made a ton of progress since I first spoke about it last fall , and with a beta version ready in a few weeks, I'm excited to share more about what we're launching.

DeltaDB breaks your work into a stream of fine-grained deltas . Where Git captures a snapshot at each commit, DeltaDB captures every operation in between and gives each one a stable identity. Because every delta can be addressed on its own, you can point to the code at any moment in its evolution, even as it keeps changing. That lets us version a worktree as it evolves, together with the conversation driving it.