Zed Introduces Version Control System DeltaDB: Operation Log instead of Commit, Blending Discussion with Code Changes

According to Dynamic Beating monitoring, Zed founder Nathan Sobo announced the development of a new generation version control system called DeltaDB for the Zed editor. Unlike traditional Git commit snapshots, DeltaDB records every fine-grained edit operation (Delta) and assigns a unique identifier. Developers can jump to any moment in the code's evolution history, addressing the pain point of disconnect between code changes and development discussions.

DeltaDB integrates development discussions with code changes directly. Code references are anchored to specific Deltas, not relying on fixed file line numbers. Even if the code is later moved or modified, the reference links remain valid. Developers can directly jump from any sentence in the historical conversation to the corresponding code version; they can also trace back related development discussions from any line of code. The AI agent can read the entire history of evolution directly and even summon the AI agent from previous work to inquire about the code's design intent.

The system incorporates Conflict-free Replicated Data Type (CRDT), supporting real-time collaboration across devices among multiple developers and AI agents to modify files. The workspace can be accessed via the terminal or mounted directly to the local disk to integrate with external development tools. In the AI agent development mode, the conversation itself is the true source of the software. DeltaDB merges discussions with code into the same space, eliminating the cumbersome process of traditional Pull Requests and Code Reviews. Currently, DeltaDB has opened testing reservations and is expected to start Beta testing in a few weeks.