Zed's AI-Native Version Control Tool Just Opened Early Access. It Tracks Every Edit, Not Just Every Commit.
Zed's AI-Native Version Control Tool Just Opened Early Access. It Tracks Every Edit, Not Just Every Commit.
DeltaDB, the version-control system Zed first announced back in June, opened Early Access on August 6 and immediately climbed the Hacker News front page again: over 260 points and well past a hundred comments within a few hours. I've written about Zed's parallel-agents feature on this blog before, and DeltaDB is the more ambitious bet underneath that work: instead of snapshotting your code at each commit the way Git does, it records every individual edit operation, and ties each one to the conversation that produced it.
If you run Claude Code or Codex against a real project and have ever lost the thread on why an agent made a specific change three sessions ago, this is aimed directly at you.
What DeltaDB actually does
Per Zed's own announcement, DeltaDB breaks your work into a stream of fine-grained "deltas" instead of commits. Where Git captures a snapshot each time you commit, DeltaDB captures every operation in between and gives each one a stable, addressable identity. Because each delta is anchored to itself rather than to a line number, a reference to it survives even as the surrounding code keeps changing underneath it.
The part that's genuinely new, not just a finer-grained Git: a message and the edit it produced are recorded side by side, so the conversation and the code don't drift apart the way a Slack thread and a pull request inevitably do. From any point in a past conversation, you can jump to what that code looks like now, or what it looked like the moment the agent wrote it. From any line of code, you can find the conversation that produced it, and every conversation that's touched it since.
Why Zed thinks Git is the wrong shape for agent-driven coding
The argument, laid out by Zed founder Nathan Sobo when the project was first announced, is that the conversation generating your code has quietly become the real source of your software, and Git was never built to keep that conversation attached to the code as it evolves. Pull requests and review threads exist to reattach a discussion to code after the fact, because historically the discussion and the code lived in separate places. Put them in the same place, the argument goes, and a lot of that ceremony becomes unnecessary. Git and CI still handle what they're good at: running checks and connecting your work to the rest of the world.
Whether you buy the full pitch or not, the specific problem it's solving is real. Anyone running an agent against a codebase they don't fully understand has felt the moment where a change makes no sense, and the "why" behind it exists only in a closed terminal window from two days ago.
The detail that decides whether this is useful outside Zed's own editor
DeltaDB runs over the Agent Client Protocol, the same open protocol behind Zed's parallel-agents feature. Per commenters testing it in today's Hacker News thread, that means it isn't locked to Zed's own built-in agent. It can front Claude Code or Codex running in a Zed terminal session too, which matters a lot if your actual workflow already spans more than one coding agent rather than living entirely inside one vendor's assistant.
What's backing this, and what license you're actually trusting
Zed Industries closed a $32 million Series B, led by Sequoia, in August 2025, explicitly framed around a pivot from "build the fastest editor" to "build the way humans and agents collaborate on software." Both Zed and DeltaDB are open source with an optional paid layer on top, which is worth checking directly before you commit a real project's history to it. Open source doesn't automatically mean self-hostable in the way you'd want for a full version-history system, so read the actual license and hosting story rather than assuming.
The honest counter
This is genuinely early. It's Early Access, not a general release, and several commenters in today's thread compared it, not unfairly, to "Local History," a feature JetBrains IDEs have shipped for years. It also doesn't replace Git for anything that needs to interoperate cleanly with GitHub, your CI pipeline, or a teammate who isn't using Zed's tooling. This is additive to your existing version control today, not a replacement for it, and treating it as a full Git swap-out before it's proven itself over months of real use would be the wrong read.
What I'd actually do
Try it on a side project, not a production repo. If you're already running Claude Code or Codex regularly and have felt the specific pain of losing context on why an agent did something, DeltaDB is a concrete, testable bet on solving that structurally instead of pasting chat transcripts into a wiki after the fact, which is what most of us do today. Connect it through a Zed terminal session on something low-stakes, watch whether the delta-to-conversation links actually hold up over a few days of real editing, and decide from there whether it's worth building a permanent habit around. I wouldn't move a client project's history onto it yet. I would put it on my own list of things to revisit once it's out of Early Access.
Author
Lukas
@lukcombinator