Fetching from the wire…
01
02
03
04
05
06
07
08
Tools2026-08-06 · source-backed
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 progress without commit/push gates. Zed has published no architecture, language, licensing or performance detail, and it's email-gated early access. So this is positioning, not something you can evaluate. But "commits are the wrong granularity for agent work" is the right problem statement, and nobody else has said it this clearly.
Each link below shares sources, entities, or timing with this story.
Shared entity: Each / Shared topic / Earlier coverage / Downstream implication
Both cover Each; overlapping topics (agent, architecture, between, each); earlier Each coverage from 2026-03-24.
Shared entity: Each / Shared topic / Earlier coverage / Tension
Both cover Each; overlapping topics (access, agent, architecture); earlier Each coverage from 2026-03-25.
Shared entity: Each / Shared topic / Earlier coverage
Both cover Each; overlapping topics (agent, architecture, commit, each); earlier Each coverage from 2026-05-02.
Shared entity: Each / Shared topic / Earlier coverage / Tension
Both cover Each; overlapping topics (agent, each); earlier Each coverage from 2026-07-22.
Both cover Each; overlapping topics (agent, each); earlier Each coverage from 2026-02-27.
Shared entity: Each / Shared topic / Earlier coverage
Both cover Each; overlapping topics (agent, comment, each); earlier Each coverage from 2026-06-28.
Both cover Each; overlapping topics (access, agent, each); earlier Each coverage from 2026-05-10.
Both cover Each; overlapping topics (agent, each, edit); earlier Each coverage from 2026-04-12.