September 25, 2026
Delta helps unpack a large unfamiliar change: subthread takes the context
On Sep 24, Delta demonstrated reviewing a change spanning thousands of lines through a subthread. The new thread receives its parent’s context when it launches, then works in a separate worktree. Delta is in public beta. Personal costs $0 with external agents or your own API keys; Pro costs $10 per month and includes $5 in tokens.
Zed
@zeddotdev
Here is one of our development workflows in Delta. @nathansobo shows how he investigates a Delta feature that @as__cii and Cole are working on: to understand the intent behind a change spanning several thousand lines, he uses a subthread.
· 3.2K views
To understand the intent behind a large change made by someone else, you had to reconstruct it from the changed lines and discussion. Now Delta creates a subthread with Cmd+Shift+Enter on macOS or Ctrl+Shift+Enter on Linux and Windows. It receives the parent thread’s context and handles the task separately.
A subthread’s changes do not return to the parent worktree automatically. The parent agent must merge them. For review, Delta creates an isolated copy of the worktree, gives the reviewer the original agent’s context, and lets you enable fixes before landing.
Joining the beta. You need a Zed account and acceptance of the Delta Early Access Agreement. Delta runs on macOS 13+ with Apple Silicon, Linux with glibc, and Windows. On macOS, unzip Delta.app.zip, move the app to /Applications, and run `xattr -dr com.apple.quarantine /Applications/Delta.app`.
Models are available from Zed, ChatGPT, GitHub Copilot, and Grok, as well as 5 API-key providers. Git stores a snapshot at each commit, while DeltaDB records every human and agent edit in sequence: you can comment while an agent is working and roll back together with the worktree.
In Delta’s own repository, the Zed team has disabled pull requests: 33 people made 570 changes directly to main.
Source
