--- title: "Introducing Delta — Zed's Blog" url: https://daily.dev/posts/introducing-delta-zed-s-blog-mntyhpe1d source_url: https://zed.dev/blog/introducing-delta type: article source: "Zed" published: 2026-08-12T18:06:20.049Z updated: 2026-08-12T23:14:09.963Z tags: ["ai-agents", "claude-code", "zed"] reading_time: 6 upvotes: 4 comments: 1 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Introducing Delta — Zed's Blog **[Zed](https://daily.dev/sources/zed)** · 6 min read · 4 upvotes · 1 comments ## Summary Zed has launched Delta, a new multiplayer environment for coding with AI agents and reviewing their output, now open for private beta signups. Built on DeltaDB, a real-time database that syncs conversations and code together, Delta lets teams comment on any line of code or conversation, invite collaborators into threads, run agents in the cloud, and connect to third-party agent harnesses like Claude Code. Delta is a standalone Rust application (compiled to WebAssembly for browser use), separate from the Zed editor, though DeltaDB capabilities will eventually come to Zed too. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is Delta from the Zed team and how is it different from the Zed editor? Delta is a new standalone multiplayer application for coding with AI agents and reviewing their work, built by the Zed team, currently in private beta. Unlike Zed the code editor, Delta centers the conversation with agents rather than the editor, runs on DeltaDB (a real-time database that syncs code and conversation together), and is a separate Rust app compiled to WebAssembly for browser access. _daily.dev tracks new agentic coding tools like Delta as teams evaluate where AI-assisted workflows are heading._ ### Does Delta integrate with Claude Code for agentic coding sessions? Yes, Delta connects to third-party agent harnesses starting with Claude Code. Developers can keep working in their existing terminal, and the session syncs live into a Delta thread, letting teammates watch the conversation and code evolve, comment in place, and pick up the work with full context. _developers weighing agent harness integrations can follow tools like Claude Code and Delta on daily.dev._ ## Community take How the wider developer community reacted, aggregated from 2 discussions and 105 comments across lobsters, hackernews (as of 2026-08-12). **TL;DR:** Reaction is heavily skeptical, with many questioning why Delta's DeltaDB features and multiplayer chat-review model add real value over existing agent harnesses, while a smaller group who tested the alpha found the inline-comment-on-conversation workflow genuinely useful. **Sentiment:** 20% positive · 30% mixed · 50% skeptical **The case for** - Testers who used the alpha said annotating directly inside agent conversations/diffs solved a real pain point of writing lengthy bullet-point replies to guide agents. - Some see value in preserving agent conversation transcripts as a record of design reasoning and decisions, useful for onboarding or auditing. - A few think it could help mentor or onboard less experienced contributors by letting others see how an agent-produced PR came about. **The pushback** - Many doubt real teams actually want to collaborate live inside an editor or agent chat, arguing coding/review is mostly solitary work. - Several argue the underlying DeltaDB advantages are unclear or no longer differentiated given how much frontier models and other agent tools have advanced in the past year. - Concerns that Delta will introduce vendor lock-in benefiting investors more than users. - Frustration that Zed keeps shipping AI-adjacent products while its core editor is seen as buggy, stagnant, and increasingly indistinguishable from VS Code. - Criticism that it isn't open source, unlike Zed itself. - Complaints about the announcement's poor page contrast/readability and lack of a demo video making the product hard to understand. - Broader tangent thread criticizing verbose/unreliable AI-generated code summaries as low-value compared to reading code directly. **By community** - lobsters (mixed): No substantive discussion content was provided for this provider. - hackernews (skeptical): A large, sprawling thread mixes pointed skepticism about Delta's value proposition and Zed's direction with a smaller contingent of alpha testers praising the inline-annotation workflow. **Hottest debate:** Whether multiplayer/collaborative review of AI agent conversations is a genuinely needed workflow or a solution in search of a problem, since most say coding and review remain solitary activities. **Open questions** - What concrete advantage does DeltaDB provide over existing coding-agent harnesses and tools like git worktrees or Codex's annotation features? - Will Delta or DeltaDB become open source like Zed itself? - How will collaborative transcript review actually be used in practice by teams, given most describe agent work as solo? - Is there a public demo or clearer explanation of what the product looks like in use? **Highlights** > I think Zed is an excellent editor (fast!) with a pretty good AI agent built-in, but I have no desire to do multi-player development in my editor. Never have had any such desire. Coding is a single-player game and I can't think of a single thing that would be improved by having someone else in the same editor. So, this seems like a lot of work on really cool tech for no useful purpose at all? Are there people crying out for a multi-user code editor? I mean, we have to have code reviews, sure. That involves other people or other agents. But, I don't need to stand over someone's shoulder while they work. That seems like the worst thing in the world for everyone involved. I don't want an audience for my dumb looking experiments because I forgot how to do something. > — [SwellJoe on hackernews](https://news.ycombinator.com/item?id=49279669) > I'm sure this seemed like a great idea a year ago (they first mentioned it with their Series B). But a lot has changed in those 12 months. Frontier models and coding agents have advanced so much that I don't really see much value in this anymore. Not sure the DeltaDB based features really add anything significant here compared to the alternatives. I reckon the game here has to be adding a service that stores the data and runs agent sessions? > — [the\_duke on hackernews · 2 comments](https://news.ycombinator.com/item?id=49276928) > This is intriguing. The two relevant features seem to be 1) realtime collaborative multiplayer conversations and 2) conversation-as-document - basically, letting you comment inline in an agent conversation. For (1), the main value I'd see is in mentoring junior engineers or less technical contributors on a team. If someone puts up a PR with sloppy results, you could actually jump into the thread that produced that PR and see how the results came about, or even coach that contributor on how to do better next time. Also might make it easier to hand off work from one person to another - right now most coding agent sessions are user-local. On (2), I frequently find myself consuming agents' gigantic text responses and tediously writing 8-bullet-point responses to guide them. It's pretty exhausting. I could see inline comments providing much better ergonomics. All that being said, Zed has largely fallen out of the conversation for "agentic coding tools", and so this feels like their attempt at creating something like the Cursor Agents Window, Codex, or Claude Code. These two features seem compelling, and I understand they're even compatible with other coding harnesses. But I don't know if there's enough there to have a defensible product; if these features are excellent, others will clone them eventually. Regardless, would love to give this a shot! > — [vipshek on hackernews · 3 comments](https://news.ycombinator.com/item?id=49277029) > > We could have added DeltaDB to Zed, and eventually we will. But the best possible experience required an entirely new kind of application The following demo is a version of a text editor - a chat window and a diff. How would building a new limited text editor be the best possible experience? Like you've setup your Zed schemes/keybinds to your liking, why would jumping to a totally different app improve your experience? > — [eviks on hackernews · 1 comments](https://news.ycombinator.com/item?id=49278965) > Honest question, do any of you actually use this type of multiplayer feature in editors? I have worked on small, medium, large and FAANG(Google and Amazon) companies. Never have I seen anyone, even talking about coding with somebody else in the same editor. Edit: grammar > — [j\_rosenberg on hackernews · 1 comments](https://news.ycombinator.com/item?id=49278302) **Source threads** - [lobsters](https://lobste.rs/s/go39b7/zed_introducing_delta) · 1 points · 0 comments - [hackernews](https://news.ycombinator.com/item?id=49276574) · 306 points · 105 comments ## Community discussion Top comments from developers on daily.dev. **@khauma** · 0 upvotes > This is major!!!!! --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#claude-code](https://daily.dev/tags/claude-code), [#zed](https://daily.dev/tags/zed) [View this post on daily.dev](https://daily.dev/posts/introducing-delta-zed-s-blog-mntyhpe1d)