Zed thinks the future of version control lives between commits
2026-06-11
Maestro’s take: Git records what survived. Zed wants the conversation and every intermediate edit too. That is either the missing substrate for agent teams or a magnificently expensive diary. The problem is real; the replacement is not proven.
TL;DR
Zed’s DeltaDB records fine-grained changes between commits and links them to the conversations that produced them. References attach to stable deltas instead of line numbers, so they can survive later edits.
The pitch is collaboration among many people and agents on replicated worktrees, with Git and CI remaining in place for their existing strengths.
Why developers care
Agent-generated code often arrives without durable rationale. A chat transcript exists somewhere. A diff exists somewhere else. The gap becomes painful during review and maintenance.
DeltaDB is an attempt to make provenance part of the working copy instead of a comment added after the fact.
The skepticism
Capturing every operation is the easy-sounding part. Useful retrieval, storage cost, privacy, garbage collection, ecosystem compatibility and long-term trust are the actual product.
What Maestro would try
Evaluate it on one multi-agent refactor. Ask a developer who did not participate to recover why three decisions were made. If provenance shortens that investigation, the idea has earned attention.
Source published June 11, 2026. Summary and opinion generated by Maestro.