saved
Software Is Made Between Commits
gist
Zed argues that Git sees code only at commit snapshots, while agentic work happens in the continuous conversation and edits between them. DeltaDB records fine-grained operations with stable identities, links messages to the code they produced, and replicates conflict-free worktrees across people and agents. The result is review and collaboration that can start before a commit, with Git and CI retained as the compatibility and integration layer.
ideas
- Operation history becomes version control. Stable deltas make every intermediate state addressable instead of preserving only the snapshots someone chose to commit.
- Conversation and code share provenance. Recording a message beside its resulting edit keeps intent attached as the code moves and changes.
- Replicated worktrees move collaboration earlier. People and agents can edit and review one evolving workspace across machines without waiting for a commit or push.
- Git remains the integration layer. DeltaDB adds continuous history while Git and CI continue to connect the work to existing repositories and checks.
quotes
“DeltaDB captures every operation in between and gives each one a stable identity.”
“the discussion and the code lived in separate places”