GoKawiilToday, we're launching the public beta of Delta, a multiplayer environment for coding with agents and reviewing what they build. We're building Delta because agents have fundamentally changed the way we write software, but our collaborative tooling isn't keeping up.
Last week, we crossed a key milestone: we disabled pull requests on Delta's own repository. We now build and collaborate on Delta entirely within Delta.
Pull Requests are seriously turned off.
What makes Delta different from traditional workflows is that collaboration doesn't depend on committing and pushing code. You invite teammates directly into your conversations with agents. When someone joins your thread, they see the same worktrees you do and can work with them on their own machine. Teammates can ask the same agent why you chose a Mutex instead of an RwLock . If you log off, they can keep working with the agent where you left off.
Starting today, anyone can download Delta for macOS, Linux, or Windows, use it on the web without downloading anything, and keep up with threads from a mobile browser on the go.
Richard Feldman walks through an end-to-end flow in Delta: fixing an issue, getting a teammate's review, and merging it.
Since GitHub introduced pull requests over 15 years ago, they've become the standard way to ask teammates to review changes to your codebase. But with agents generating so much code, the diffs we're asking each other to review have mushroomed.
Splitting a big diff across a stack of branches can make it easier to navigate, but the decisions behind the code still need review. Smaller diffs don't supply that context. A reviewer may feed your diff into another agent to help understand it, but that agent has to piece together decisions you already worked through.
Why should your teammate's agent have to guess how you got there?
In Delta, you can invite anyone to pick up a thread where you left off, or create a dedicated review subthread. A review guides you through your branch's changes with access to the original agent's context. Each review gets its own isolated copy of the parent thread's worktrees, so you and your teammates can use agents to explore the code and try changes without disrupting the original work. If a reviewer spots a problem, they can request a revision or work with an agent to fix it themselves. Fixes made during review can be incorporated into the parent thread before you ask the agent to land the change.
... continue reading