More on the topic...
Generating detailed summary...
Failed to generate summary. Please try again.
Zed’s team grew tired of pull requests and the delayed code discussions they force. They’ve worked side by side in the same worktree for years, talking through edits as they happen rather than trading comments on snapshots. When Git demands you push and commit before you can chat about code, most of the real decisions have already been made.
DeltaDB replaces Git’s snapshot model with a stream of every edit operation. Each tiny change gets a stable ID, so you can point to the code at any moment—past or present. Messages and the edits they spawn live together. Multiple people and AI agents can edit the same files in parallel, thanks to built-in conflict-free replicated worktrees. Those files are real on disk, so you can run tests, lint, or fire up any tool you like.
Because references anchor to deltas instead of line numbers, comments never drift when code moves. Jump from any line in an old conversation to its original code or the latest version. Agents can see why a piece of code exists, fetch past discussions, and even call in other agents that touched it before. This tight link between talk and text turns source into a “source conversation,” not just source code.
The goal: eliminate the commit ceremony. Teammates and agents join ongoing work live, annotate as they go, and skip pull-request paperwork. Git and CI remain for builds and sharing, but collaboration happens inside DeltaDB. A public beta is scheduled in a few weeks, and you can join the waitlist now.
Questions about this article
No questions yet.