Back
Zed opens early access to DeltaDB, version control for the agent era
SiTech Team2 წთ. საკითხავი

Zed opens early access to DeltaDB, version control for the agent era

Zed Industries has opened early-access signups for DeltaDB, a version control system that records the work between commits and ties every change to the agent conversation that produced it.

Zed Industries, the company behind the Zed code editor, has opened early-access signups for DeltaDB, a version control system built around the way AI coding agents work. The product page puts the idea in one line: software is made between commits.

What DeltaDB keeps

Conventional version control stores snapshots. A developer edits files, creates a commit, and pushes that snapshot for review. Everything that led to it — the prompts, the failed attempts, the corrections, the abandoned edits — is discarded. DeltaDB is built to keep that intermediate work instead: it records every operation between commits and gives each one a stable identity, so any moment in the code's evolution can be pointed to directly.

Access is currently handled through a signup form that asks for an email address and a GitHub username under a “Request Early Access” button. The page states the information will be used only to contact applicants about the early access program.

Four claims on the page

Rewind to any edit: because every operation carries a stable identity, the code state at any point in its history can be reconstructed. Trace code to conversation: each change is linked to the agent conversation that produced it, so a line of code can lead back to the message behind it, and any message can jump to the code it touched. Branch at any moment: DeltaDB virtualizes the worktree, which makes spinning up a new agent branch, in Zed's words, effectively free — any point in history is a valid branch point, including mid-run. Share the thread, not the PR: a teammate can join while the work is still happening, talk to the agent that did the work, and annotate as they go, without waiting for a commit and push.

Why it matters — and what is missing

As more code is written by agents rather than typed by people, the space between commits holds much of the reasoning: what was asked, what the agent assumed, what a human corrected. A commit history cannot represent that, which is the gap DeltaDB targets. Zed has not published a technical specification, performance benchmarks, supported repository sizes, or details on how the system works with existing Git hosting, so its production readiness cannot yet be judged. On the company's account, Git and CI remain the layer for publication and interoperability, with DeltaDB supplying finer-grained history beneath them.

SSiTech

SiTech — AI-powered web development

We build fast, modern websites and bring AI into real business workflows. Have a project or a question? We'd love to help.