Fetching from the wire…
Public story · 2026-09-18 · high
Reviewers join the agent conversation itself, worktrees included, instead of reading a final diff.
Why now: Zed put the beta up on September 16.
Zed launched a public beta of Delta on September 16, and it drops the pull request entirely. Instead of pushing a branch and waiting for a diff review, you invite a reviewer straight into the thread where you and an agent worked out the change. They can see your worktrees, ask the agent why it made a given choice, and open a review subthread with its own isolated worktree copy to test a fix without touching the original.
The engine under this is DeltaDB, which extends Git to record incremental edits instead of only the final state. That's a real shift in what gets preserved. A normal PR shows you the after; DeltaDB keeps the sequence of edits that got there, so a reviewer can watch the path the agent took, not just the destination.
Zed's diagnosis of the problem is sound. PRs built for human-authored diffs break down on agent-authored ones, because the person reviewing never had the context the agent had while writing the code. Handing reviewers the thread instead of the diff is a direct fix for that gap.
Where I'm skeptical is scale. "Read the diff" is a bounded task. "Read the agent's transcript, plus the worktrees, plus ask it follow-up questions" is open-ended, and it asks more of a reviewer's time, not less. That trade might work fine on a two- or three-person team where the reviewer already has context on the project. On a larger team reviewing code from engineers they don't work with daily, a conversational thread is a much bigger thing to absorb than a diff with a line count.
Delta is free during the beta. Worth trying on something small before betting a team's review process on it.
Each link below shares sources, entities, or timing with this story.
Zed opened private beta on August 12 (585 points on HN) for a multiplayer app built on DeltaDB, a version control system recording fine-grained deltas with stable identities rather than snapshots. Every change links bidirectionally to the agent conversation that produced it, a...
Zed's Delta attacks version control. Ito attacks review, spinning up an ephemeral container per PR with real credentials, seed data, and external services to return runtime evidence instead of static analysis. Kane CLI attacks verification, emitting NDJSON in agent mode so Cla...
The most useful thing I've read about agent engineering this month isn't about models. It's about harnesses. Addy Osmani published Agent Harness Engineering, and it's the kind of post where every paragraph contains something I want to steal for my own projects. The core argume...
Announced August 5, topping HN at 455 points and 241 comments. Each operation between commits gets a stable identity tied to its originating agent conversation, the worktree is virtualized so spinning up a new agent branch is "effectively free," and teammates can join work in...
Eight thousand stars in a single day. That's what happened when Warp open-sourced its Rust-based, GPU-accelerated terminal on April 28. The repo shot to 47.9K total stars, making it the highest-velocity project on GitHub this week by a wide margin. But the interesting part isn...
Stripe published Part 2 of its Minions engineering blog, and it's the most detailed production agent architecture I've read from any company this year. The numbers alone are worth the read: 1,300+ weekly merged PRs from coding agents. But the architecture decisions matter more...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.