Software Is Made Between Commits: How AI and Vibe Coding Are Redefining Version Control with DeltaDB

## Introduction For decades, software development has been defined by the commit—a snapshot of code frozen in time. But what if the real magic happens *between* those commits? A groundbreaking shift is underway in the AI and Vibe Coding community, sparked by a fresh insight from the team at Zed: **Software Is Made Between Commits.** The conversation—the iterative, messy, and creative process of coding—has become the true source of our software. Enter **DeltaDB**, a version control system built not for static snapshots, but for the dynamic flow of changes. In this article, we’ll explore why this matters, how it works, and how you can harness it today. ## The News: Zed’s Vision On June 18, 2026, Zed published a blog post that turned the developer world on its head. Their central claim? That AI agents and Vibe Coding have shifted the locus of software creation from the final commit to the ongoing dialogue between developer and machine. Source. The post introduces **DeltaDB**, a new version control paradigm that tracks every incremental change, every suggestion, and every discarded idea—not just the polished end result. This isn’t just a tool; it’s a philosophy shift. ## Why “Between Commits” Matters Traditional version control (think Git) treats a commit as a checkpoint. But in the age of AI coding assistants, the real value lies in the **iterative refinement** that happens before the commit. Consider these scenarios: - **Vibe Coding**: You describe a feature in natural language, the AI generates code, you tweak it, and repeat. The “commit” is just a snapshot of the final version, but the knowledge of *why* you made each change lives in the conversation. - **Agent Collaboration**: Multiple AI agents propose solutions, you accept or reject them. The decision-making process is lost if only the final code is saved. DeltaDB captures this *between-state*—every edit, every suggestion, every thought that shaped the software. This is a game-changer for **code provenance**, **debugging**, and **team collaboration**. ## How DeltaDB Works: A Practical Breakdown DeltaDB doesn’t replace Git; it augments it. Here’s what it brings to the table: | Feature | Traditional Git | DeltaDB | |---------|----------------|---------| | **Granularity** | File-level snapshots | Line-level, change-by-change tracking | | **Context** | Commit messages | Full conversation history with AI/agents | | **Replay** | Hard to replay decisions | Easy to replay the exact sequence of changes | | **Storage** | Git objects | Delta stream database | For example, imagine you’re building a React component. With Git, you might have 3 commits. With DeltaDB, you can see the 27 incremental steps—including the AI’s first attempt, your edit to fix a bug, and the final polish. This makes **code review** richer and **onboarding** faster. ## Practical Use Cases Here’s how you can use this *between-commits* approach today: 1. **Debugging with AI**: When an AI agent introduces a bug, DeltaDB lets you trace back to the exact suggestion that caused it. No more guessing. 2. **Learning from Past Iterations**: New team members can replay the entire development conversation, understanding not just what code was written, but *why*. 3. **Auditing Agent Behavior**: If you’re using multiple AI models, DeltaDB records which agent made which change, enabling **agent accountability**. 4. **Vibe Coding at Scale**: For large projects, tracking the *vibe*—the continuous refinement—becomes as important as the code itself. ## The Bigger Picture: Vibe Coding and AI Agents Vibe Coding isn’t just a trend; it’s a new paradigm where developers orchestrate rather than type. The *between-commits* space is where **human intuition** meets **machine speed**. DeltaDB acts as a **digital memory** for this partnership, preserving the context that makes software truly collaborative. As AI agents become more autonomous, having a record of their decision-making process is critical for trust and reliability. ## Conclusion The notion that “Software Is Made Between Commits” challenges everything we thought we knew about version control. DeltaDB, born from Zed’s insight, is not just a tool for the AI age—it’s a mindset shift. Start treating your coding conversations as the real artifact. Use DeltaDB to capture the flow, not just the freeze. The future of software development is iterative, conversational, and beautifully messy. Embrace the between. *Ready to dive deeper? Check out the original post at Zed’s blog and start experimenting with DeltaDB in your next Vibe Coding session.*

Software Is Made Between Commits: How AI and Vibe Coding Are Redefining Version Control with DeltaDB

Comments

Recent articles

Documentation Index: The New Standard for AI Context in Vibe Coding

Flutter and Dart — Cross-Platform Development: Why 2026 Became a Turning Point

Cian API and AI Agent: How to Automate Real Estate Market Analytics in 2026

AI Model Distillation: Shrinking Giants into Speed Demons for Real-World Deployments

AI-Native Startups in 2026: Building Companies Entirely Around LLMs

AI Testing: How to Test AI Applications and Models to Avoid Missing Bugs in 2026

Replit | Databricks: Where Fast App Building Meets Granular Data Governance

AI Climate Change: How Machine Learning Revolutionizes the Fight Against Global Warming

Why AI Terms and Policies Just Got a Major Overhaul: What Developers Need to Know