Zed opens early access to DeltaDB, a version control system linked to agent conversations

Key facts

• Zed Industries has opened early access signups for DeltaDB, a version control system built around AI coding agents, framed on its product page by the line "software is made between commits."
• DeltaDB gives every operation between commits, not only the commits themselves, a stable identity, so a developer can point to the code at any specific moment in its history.
• Every code change is linked to the agent conversation that produced it: from any line of code the tool surfaces the conversation that wrote it, and from any message in that conversation it can jump to the code the message touched.
• DeltaDB virtualizes the working tree, so starting a new agent branch is described as "effectively free," and any recorded point in history, including a moment mid-run, is a valid branch point.
• A teammate can join a session while an agent is still working and annotate it live instead of waiting for a commit and push; signing up requires only an email and GitHub username, and the page discloses no pricing or timeline for DeltaDB itself.

Why it matters

DeltaDB's own pitch is a single line on its page: "software is made between commits." A conventional version control system like git only keeps the snapshots a developer chooses to save, so everything that happens between two commits, including whatever back and forth produced an AI agent's changes, normally disappears once the commit lands. DeltaDB instead gives every operation between commits a stable identity and keeps each one tied to the agent conversation that produced it, so a reviewer is not left with only a diff and no record of why an agent made a particular change or what it was asked to do. As more code gets written by agents rather than typed directly by a person, that missing middle, the conversation and the intermediate edits, is exactly what a plain commit history cannot represent, and it is the gap this product targets.

Who it affects

Developers who already use, or are considering, AI coding agents for real work, since the product is built specifically around keeping a durable link between an agent's conversation and the code it produces. Team leads and reviewers gain a more direct way to check an agent's progress: the "share the thread, not the PR" feature lets a teammate join a session while an agent is still running and talk to it directly, instead of only seeing a finished pull request after the fact. Teams doing collaborative, multi-agent development stand to benefit from cheap branching, since DeltaDB's virtualized working tree is meant to make starting a new agent branch, including from a point mid-run, effectively free. For now this reaches only people who sign up for early access with an email and GitHub username; the page does not say whether using DeltaDB requires the Zed editor itself or works alongside other editors and agents.

How to use it

Access is currently limited to a wait list. Signing up takes an email address and a GitHub username, submitted through a "Request Early Access" button, and the page states that information will be used only to contact the signee about DeltaDB's early access. The page gives no price or plan for DeltaDB itself, no date for when early access will open to people who sign up, and no general-availability timeline; the site's general "Pricing" navigation link points to Zed's existing pricing rather than anything specific to DeltaDB. Once inside, the described workflow centers on the four features on the page: pointing to the code at any past operation, jumping between a line of code and the conversation that produced it, branching from any recorded moment including mid-run, and having a teammate join and annotate a session while it is still in progress.

How solid is it

Every claim here comes from Zed's own product page for a product that has not shipped yet, and nothing on the page is independently verified. No engineer, founder or spokesperson is named or quoted about DeltaDB, and the page cites no customer, case study or outside test of the four described features. It gives no technical detail on how operations get their "stable identity" or how the virtualized working tree is actually implemented: no storage format, backend or protocol is named. On Hacker News, where the story was submitted by user "ahamez," it reached 340 points and 183 comments within about 10 hours, a velocity of roughly 34 points per hour; that is a strong engagement signal, but it measures attention to the announcement, not outside confirmation that DeltaDB works as described, since nothing beyond the sign-up form is available to try yet.

Risks and caveats

Because DeltaDB is gated behind an early-access sign-up, the four capabilities on the page are stated intentions rather than behavior anyone outside Zed has been able to test. Several practical details are missing: pricing, a release timeline, whether DeltaDB requires the Zed editor specifically or works with other editors and coding agents, and how sensitive material stays protected once a teammate can join a session mid-run and see an agent's conversation along with the code it touched. The tagline "software is made between commits" is worth reading as a pitch rather than a settled fact until the product ships and can be reviewed independently.

“DeltaDB captures every operation in between commits and gives each one a stable identity, so you can point to the code at any moment in its evolution.”

— Zed, on the DeltaDB product page