August 2026 Summaries

Delta is a new multiplayer application from the Zed team, now entering private beta, designed to keep AI-agent conversations, code changes, reviews, and project history connected in a shared workspace. Built on DeltaDB, it synchronizes conversations and worktrees in real time while remaining compatible with existing Git repositories and normal commit and push workflows. Users can comment on evolving code, diffs, plans, and conversation text, allowing teammates and agents to retain the context behind implementation decisions rather than relying solely on static commit snapshots. Delta supports local collaboration, cloud runners that continue agent work after a user disconnects, browser-based access through a WebAssembly version of the Rust application, and third-party agent tools beginning with Claude Code. The company created Delta as a separate application rather than immediately integrating the technology into Zed, aiming to develop an interface centered on conversational, agent-assisted software development while continuing work on Zed and planning future DeltaDB integration.

Zed 1.14 enables operating-system-enforced sandboxing by default for its agent panel’s terminal and fetch tools, restricting writes outside project directories, changes to .git, and network access unless users grant temporary or permanent elevated permissions with an accompanying reason. Implemented through macOS Seatbelt, Linux namespaces via Bubblewrap, and WSL on Windows, the feature is intended to provide stronger protection than instruction-following or command-based rules, particularly against prompt injection and malicious project files. The discussion highlights the complexity of secure sandbox design through a potential symlink-swap time-of-check-time-of-use attack, which Zed addresses by failing closed, while emphasizing that even narrow timing vulnerabilities must be treated seriously. Sandboxing is presented as one defense-in-depth layer rather than comprehensive protection, since other editing tools, external terminals, language servers, build scripts, procedural macros, and Git hooks may still execute harmful code outside its scope.