Introducing Delta Zed Blog

Pippa This matters because agent-generated code is turning review into archaeology. Delta is Zed trying to keep the prompt, the edits, and the objections in one place.

Tyler And it’s a real product bet, not another tiny agent panel bolted onto an editor. They made a separate application because their underlying replication model wanted to be the center of the experience.

Pippa Right.

Tyler That’s a costly choice, but I kind of respect it. Retrofitting this beneath Zed’s existing users could have broken workflows they already depend on.

Pippa Also, hi. This week has had that very specific feeling where every tool claims it solved collaboration, and then it means a shared sidebar.

Tyler Mm-hm.

Pippa Delta at least appears to mean something stronger. It says the worktree itself is collaborative, which is the part that makes my product brain sit up.

Tyler I am staring at the phrase “multiplayer worktree” like it owes me an implementation document.

Pippa That is because joy enters your system as an untrusted dependency.

Tyler Fair. Keep going.

Pippa DeltaDB replicates the conversation and the worktree together in real time. Each person gets a local copy of the code, kept in sync, while Git still works normally for commits and pushes.

Tyler Exactly.

Pippa So teammates who never open Delta just see a normal repository. That compatibility is the adoption story, because nobody has to declare a version-control revolution before trying a new review flow.

Tyler The technical move is finer-grained than Git’s commit snapshots. DeltaDB uses C R D T-style incremental synchronization, and that is why it can track live edits and discussion without making a commit the only meaningful unit of history.

Pippa Yeah.

Tyler The clever part is where that goes in review. A comment can attach to a line in the worktree, a diff, or a particular bit of the agent’s conversation, and it stays connected as the code evolves.

Pippa Which fixes the gross little ritual where you find an old review comment, realize the file moved twice, then reconstruct what anyone meant from a diff and three terse messages. I hate that ritual.

Tyler No way.

Pippa And the agent is in the same thread. If a change looks wrong, you can point at the exact plan step or code line and ask it to explain or repair that thing, instead of sending another broad prompt into the void.

Tyler That is the part I’m most sold on. Agents emit huge transcripts and large diffs, while a lot of interfaces respond by hiding the evidence, which is just the throughput trap wearing a nicer jacket.

Pippa You found a way to bring episode eight fifty-one into a code editor launch.

Tyler It fits! Delta keeps full diffs and transcripts visible, then treats the conversation like an editable document. Your cursor can land on a plan item or even a thinking block, and comments are precise instead of serial messages tangled at the bottom.

Pippa Okay okay. The target user is a team already doing substantial agent work, especially where one person starts a task and someone else has to review or continue it. Private threads stay private until shared, then invited teammates can join live or pick it up later.

Tyler There’s also a cloud runner path: move the work there, close the laptop, and the agent keeps running with its code and thread synchronized. A teammate can open a shared thread in the browser, and Zed says that browser experience is the same Rust application compiled to WebAssembly and rendered with WebGL.

Pippa Naturally, you heard “WebGL” and sat up like a cat hearing a cupboard open.

Tyler I did. But I have one serious concern: real-time replicated code is only useful if the permission model, failure recovery, and Git edge cases feel boring. Their private beta is exactly where that gets tested.

Pippa They start with Claude Code, and that’s smart. You can keep using the terminal session you already have while it syncs into a Delta thread, then share the work without making everyone adopt a new agent harness.

Tyler Right, and this is round another of the harness-as-product fight. The field still hasn’t settled whether the agent belongs in an editor, terminal, or managed runtime. Delta’s answer is: preserve the harness, but make its receipts collaborative.

Pippa Fine, Exploring Next can stop pretending the boring controls aren’t load-bearing. I’m signing up for the beta, Tyler.