AI 编程 4.0 · 优秀 2026-08-12 · 文章

Introducing Delta

Zed 团队发布 Delta,把 agent 开发从终端里跑一次任务推进到多人协作空间:DeltaDB 同步 conversation 与 worktree,评论可以锚定在线程diff 和代码任意位置,云端 runner 继续执行时上下文仍同步到同一个 thread它把代码审查agent 推理和协作历史放在同一个实时复制层里

打开原文回到归档

Introducing Delta

Source: https://zed.dev/blog/introducing-delta
Author: Nathan Sobo
Original date: 2026-08-12
Added by: AAIF daily-intake-evening 2026-08-13

摘要

Zed 团队发布 Delta,把 agent 开发从“终端里跑一次任务”推进到多人协作空间:DeltaDB 同步 conversation 与 worktree,评论可以锚定在线程、diff 和代码任意位置,云端 runner 继续执行时上下文仍同步到同一个 thread。它把代码审查、agent 推理和协作历史放在同一个实时复制层里。

English Summary

Delta is a multiplayer environment for coding with agents. DeltaDB replicates conversations and worktrees together, allowing developers to review diffs, comment on code or transcript lines, and sync Claude Code-style sessions into a shared thread.

入库理由

  • quality_score: 4
  • category: coding
  • tags: zed, delta, agentic-coding, collaboration, developer-tools
  • one_liner: Delta 把 agentic coding 的会话、worktree、review 合并成实时多人协作层。

Obsidian evidence excerpt

生成 16.36×。
  摘要:TinyLlama 1.1B 跑出 4787 tok/s prompt(98% 裸金属),Gemma 4 12B 515 tok/s prompt(99.59% 裸金属),30B Muse Glimmer 194 tok/s prompt。最关键的技术边界是:这是 process-scoped 的 Metal capability shim,不是真 PCI/VFIO passthrough,依托 Apple 私有 guest Metal 实现细节,每个 host/guest 组合要独立验证。
  链接:https://github.com/trycua/cua/blob/main/blog/gpu-passthrough-macos-vms.md

- 标题:Introducing Delta
  评分:8.0/10
  推荐语:Zed 团队把「编辑器 → IDE → 协同会话」路线图最后一段做出来——DeltaDB 把 conversation 和 worktree 一起实时复制给同线程的所有人,diff 永远对着 working tree,agent 推理、评论、commit 上下文全部 anchor 在代码当前状态而非 snapshot。
  摘要:Delta 是单一 Rust 应用,编译到 WebAssembly + WebGL 跑在浏览器里,所以云端 runner 关闭笔记本之后 agent 继续干活,context 同步到 thread。对 Claude Code 已经做了 harness 集成——在 terminal 里跑的 session 会实时流到 Delta thread。
  链接:https://zed.dev/blog/introducing-delta

- 标题:Why Go is an Ideal Language for AI-Assisted Software Engineering
  评分:7.8/10
  推荐语:Google 把 Go 重新定位成 agentic-first 而不是 agentic-friendly 的语言——gofmt 强制统一格式、compatibility promise 让 Go 1.0 代码 15 年后还能跑、govulncheck 只报你真正调用的函数、gopls + 现代版的 go fix 给 agent 提供 deterministic refactor 工具链。
  摘要:核心论点是「瓶颈从 generation 移到 verification」——动态类型语言里 LLM 幻觉的 API 调用经常过 syntax 检查但生产运行时炸掉,Go 静态类型 + 编译速度让 agent 形成高效自纠循环;标准库全方位覆盖压低 AI 引入恶意依赖的概率。Go 在 agent 时代获得重估。
  链接:https://developers.googleblog.com/why-go-is-an-ideal-language-for-ai-assisted-software-engineering/

- 标题:Google Search Is Dying. What Comes Next Is Worse
  评分:7.6/10
  推荐语:把搜索基础设施崩溃放进国家数字主权框架——FiveThirtyEight 整个归档被 Disney 直接删除,Internet Archive 被出版社诉讼拖入高成本对抗,Wikipedia 流量被 AI 摘要劫走后捐赠回流断掉,Wayback Machine 还能 crawl 的网站被 news org 主动屏蔽。
  摘要:德国法院已经判 Google AI Overview 对错误陈述负责,逻辑是「你不再是中立目录而是二次创作」。文章把这条线拉到了加拿大/欧盟层面的国家信息基础设施——Qwant、Tchap、W Social,都是把 search 当 infrastructure 而不是 free consumer service 来做。
  链接:https://thewalrus.ca/google-search-is-dying/

- 标题:Compression is prediction
  评分:7.5/10
  推荐语:把压缩机(run-length、字典、概率模型)和 LLM 的训练目标对齐到同一目标函数——用更紧凑的描述建预测下一个符号的分布——通过具体 bits 数对比(run-length 224→96 bits、文本压缩 10×+)让这件事直观。
  摘要:理论主张 LLM 和无损压缩的本质是同一件事的实际意义落到三处:AGI 与无损压缩的极限等价问题、模型 fine-tune 在压缩视角下的样本复杂度、为什么更小模型在长尾分布上比大模型好的解释。可读性高于深度,但作为入门锚点合格。
  链接:https://ngrok.com/blog/compression-is-prediction

- 标题:Modular 26.5: Mojo 1.0 is h

Fetched source body

Introducing Delta

作者: Nathan Sobo
发布时间: 08/12/2026
原文链接: https://zed.dev/blog/introducing-delta

Today we're introducing Delta, a multiplayer environment for coding with agents and reviewing what they build, and we're inviting the first users into our private beta. Delta keeps code and conversations connected, so developers and agents can work together with the full context of how the code came to be.

Delta, a multiplayer environment for coding with agents and reviewing what they build.

Delta is the second half of a plan we've been executing for years: to build the best place to write code, then make it the best place to talk about code. When we first started out, not everyone understood why you'd want to have a conversation inside your IDE. Then came agents, and now talking about code is how software gets written.

To support our collaborative vision, we built DeltaDB, which replicates the conversation and the worktree together, in real time, for everyone in a thread. DeltaDB works with the git repository you already have. Every edit and conversation is captured _between_ your commits. You can commit and push like you always did, and teammates who never open Delta see a normal git repo.

We could have added DeltaDB to Zed, and eventually we will. But the best possible experience required an entirely new kind of application. Building Zed made performance and craft an obsession for us, and Delta is built on those same principles.

<video src="https://images.zed.dev/blog/introducing-delta/main-video-4.mp4&quot; controls poster="https://images.zed.dev/blog/introducing-delta/main-poster.webp&quot;&gt;&lt;/video&gt;

Picking up a thread from a teammate, adding some more comments, and moving forward with implementation.

Review where the work happened

On a commit-based platform, comments attach to snapshots and fall out of date as soon as the code changes. In Delta, you and your team can comment on anything: the conversation, or any line of code in the worktree, whether an agent touched it yesterday or a human wrote it three years ago. Everyone sees every comment in place, anchored to the code as it evolves, connected to the conversations that produced it.

And the agent is right there in the thread, working from the same original conversation and decisions as you. When something looks wrong, you don't reconstruct intent from a diff. You ask the agent to explain it or fix it. Review stays connected to the conversation and code as both evolve.

Over time, that context helps future teammates and agents understand not only what the code does, but why it took its current shape. The history stays with the code in DeltaDB, and it surfaces right where it's relevant.

<video src="https://images.zed.dev/blog/introducing-delta/diff-comments.mp4&quot; controls poster="https://images.zed.dev/blog/introducing-delta/diff-poster.webp&quot;&gt;&lt;/video&gt;

Adding comments directly in a diff and seeing them replicated in the thread.

Agentic development becomes multiplayer

Invite your team into the conversation with a click. Threads are private until you share them, and only the people you invite can see the conversation and the code. They join as first-class participants who can explore the thread, comment alongside you in real time, or continue a task later. When a teammate picks up the work, they never have to wonder whether the latest code was committed or pushed.

DeltaDB makes the worktree itself collaborative. Every participant gets their own copy of the code on their local machine, kept in sync in real time as the work happens.

<video src="https://images.zed.dev/blog/introducing-delta/collab.mp4&quot; controls poster="https://images.zed.dev/blog/introducing-delta/collab-poster.webp&quot;&gt;&lt;/video&gt;

Multiple participants iterating on a prompt.

Delta, everywhere

DeltaDB also brings multiplayer to the cloud. Move your work to a cloud runner, close your laptop, and the agent keeps going while its conversation and code stay synchronized with the thread.

Share any thread with a link, and your teammate can open it in a browser without installing anything. Delta.dev isn't a second-class version of Delta built in JavaScript and HTML. We wanted to bring you the same Rust application, compiled to WebAssembly and rendered through WebGL, so your teammate gets the same experience you do.

Delta also connects to third-party agent harnesses, starting with Claude Code. Keep working in the terminal you already use, and your session syncs live into a Delta thread. Share it, and teammates can watch the conversation and code evolve, comment in place, and pick up the work with full context.

<video src="https://images.zed.dev/blog/introducing-delta/web.mp4&quot; controls poster="https://images.zed.dev/blog/introducing-delta/web-poster.webp&quot;&gt;&lt;/video&gt;

Opening a thread in the browser.

An interface built to keep up with agents

Agents produce more text and bigger changes than any human, and most tools cope by hiding things (e.g. collapsing diffs, truncating transcripts, summarizing what you should be able to read). We've spent over a decade building text editors, so this is exactly the problem we know how to solve. In Delta, diffs open in full, transcripts stay whole, and everything renders as fast as your model can emit it.

Showing everything only matters if you can act on it. In most agent tools, the conversation is something you watch. Output streams past, and your only way to respond is the text box at the bottom. Reacting to three parts of a plan means three serial messages, or hoping the answers don't tangle.

In Delta, the conversation is a document, and your cursor works everywhere in it. Move through the thread with the same keyboard motions you use on code. When you want to respond to something, put your cursor on it and start typing. Comments attach to the exact text they're about, and nothing in the thread is off limits: a line of the diff, a step in the plan, a thinking block. The agent sees precisely what you mean, and so does everyone else.

<video src="https://images.zed.dev/blog/introducing-delta/comments.mp4&quot; controls poster="https://images.zed.dev/blog/introducing-delta/comment-poster.webp&quot;&gt;&lt;/video&gt;

Adding comments on the thread.

We built a new application for our new reality

If you've followed our work on DeltaDB, you know we haven't been specific about how the capabilities we've been building would actually reach you; that was deliberate. For a long time we assumed the answer was Zed, but as DeltaDB took shape, we realized we needed to develop it without constraints so the database and its first application could shape each other, rather than fitting new primitives into an existing editor. And rebuilding Zed's foundations underneath hundreds of thousands of daily users would have meant disrupting the workflows they rely on every day.

So DeltaDB's first client became a new application, engineered around its replicated abstractions from day one, with the conversation instead of the editor at the center. The thread is where software happens now, and the interface should reflect it.

Delta gives us a focused place to iterate quickly and improve the primitives through real product use. We'll keep developing Zed, and DeltaDB will come to it, but Delta is where it begins.

Join the private beta

The first invites to the private beta have gone out today. We'll be inviting more users over the coming weeks. Sign up if you want early access.

  • * *
  • * *

Related Posts

Check out similar blogs from the Zed team.

[

We're Not Building AI Features for the Money

  • * *

|

Featured

|

May 05, 2026

  • * *

](https://zed.dev/blog/not-building-ai-for-the-money)[

Introducing Parallel Agents in Zed

  • * *

|

Featured

|

Apr 22, 2026

  • * *

](https://zed.dev/blog/parallel-agents)[

Introducing Zed AI

  • * *

|

Featured

|

Aug 20, 2024

  • * *

](https://zed.dev/blog/zed-ai)

  • * *

Looking for a better editor?

You can try Zed today on macOS, Windows, or Linux. Download now!

  • * *

We are hiring!

If you're passionate about the topics we cover on our blog, please consider joining our team to help us ship the future of software development.