Zed's DeltaDB Rebuilds Version Control Around AI Agent Conversations
Zed's DeltaDB replaces commit-based version control with operation-level deltas that keep agent conversations permanently linked to code
- DeltaDB is Zed's new version control system that records every edit operation -- not just commits -- and links each change permanently to the agent conversation that produced it.
- Built on CRDTs (Conflict-free Replicated Data Types), it allows multiple humans and AI agents to edit the same files concurrently without merge conflicts, across machines.
- Character-level permalinks survive any code transformation, so references to code never go stale -- you can jump from any line to the prompt that wrote it, or vice versa.
- Branches are virtually free: the worktree is virtualized, so you can branch from any delta including mid-agent-run, eliminating the need for PR ceremony.
- DeltaDB is designed to complement Git, not replace it -- Git and CI remain for running checks; DeltaDB handles the continuous collaboration layer in between commits.
- A beta opens in a few weeks; sign up for the waitlist. Both Zed and DeltaDB will be open-source with an optional paid service.
Git was designed for humans trading snapshots asynchronously. It was never built for a world where an AI agent rewrites a function in seconds, a teammate needs to understand why it was rewritten, and another agent needs that context to keep going. Zed's DeltaDB is a direct answer to that gap: a new version control system that records every operation, not just every commit, and permanently ties those operations to the agent conversation that produced them.
The commit is already obsolete
The limitations of snapshot-based version control become especially apparent when working with AI agents. Real-world development often requires interaction between commits -- you need to guide agents, correct their course, and iterate rapidly, all without the overhead of creating snapshots for every exchange. Forcing every AI interaction through the commit-based workflow is, as Zed puts it, "like trying to have a conversation through a fax machine."
Increasingly, the conversation that generates the code is becoming the true source of the 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.
What DeltaDB actually does
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.
The key technical foundation is CRDTs -- Conflict-free Replicated Data Types. A CRDT is a data structure replicated across multiple machines where any replica can be updated independently and concurrently without coordination, and an algorithm automatically resolves any inconsistencies, guaranteeing that replicas eventually converge. In plain terms: multiple people and agents can edit the same files simultaneously from different machines, and the system merges everything correctly without manual conflict resolution.