Follow us
Breaking
Tech News

Zed delivers September updates for multiplayer workflows

The September 2026 Zed release introduces tabular data previews, improved JetBrains keymaps, and DeepSeek V4 support. Performance benchmarks show Zed cold-starting in 0.4 to 0.6 seconds, significantly outperforming VS Code's 1.3 seconds.

Share

The September 2026 release of Zed introduces tabular data previews for CSV, TSV, PSV, and SSV files, with sortable columns and value-based row filtering. This update includes improved Markdown table column sizing and new Git blame and stashing actions. It also improves JetBrains keymap behavior through CamelHump-style subword navigation for alt-left, alt-right, shift-alt-left, and shift-alt-right movements. This update adds support for low reasoning effort for DeepSeek V4 Flash and V4 Pro. In April 2026, Zed reached its 1.0 milestone. PlanetTools recorded Zed cold-starting in 0.4 to 0.6 seconds in April 2026, whereas VS Code required 1.3 seconds. In those same April tests, Zed’s input latency measured 2ms while VS Code required 25ms. Earlier benchmarks from May 2026 recorded Zed v1.2.6 cold-starting in 0.4 seconds against 3.0 seconds for VS Code. Zed used 222 MB of RAM whereas VS Code consumed 3,549 MB in those same tests.

Multiplayer mechanics and cross-editor protocols

Teams using Zed for multiplayer editing see each other’s cursors and edits instantly. The Collaboration Panel provides persistent project rooms through Channels and ad-hoc private sessions through Contacts and Private Calls. Sharing a project grants collaborators access to the local file system within that project. Users call teammates from the built-in contacts panel or jump to a teammate’s location to follow them around the code. The collaboration system uses CRDT-inspired conflict resolution, Lamport timestamps, and vector clocks to manage state. Developers currently discuss a proposal for an open collaboration wire protocol to allow third-party editors to participate in Zed sessions as peers. This specification would use a subset of Zed’s existing Protobuf RPC to manage session lifecycles, buffer synchronization, and presence. The proposal includes a collaboration WIT interface for WASM extensions so that tools can react to presence, buffer operations, and cursor positions, which would enable collaborative AI assistants to see all participants’ edits. This discussion also covers pluggable authentication providers to allow organizations to use their own OIDC/OAuth identity providers like Okta or Auth0 instead of requiring GitHub OAuth. If you depend on strict editor isolation, will these interoperability plans satisfy your security requirements?

Speed and AI integration

The speed advantage in Zed remains significant for developers working on large codebases.

Metric Zed (v1.3.6) VS Code
Cold Start Time 0.4 – 0.6 seconds 1.3 seconds
Idle RAM Usage 180 – 222 MB 650 – 3,549 MB
Input Latency 2 ms 12 – 25 ms
Large File Opening 0.15 seconds 1.19 seconds

Zed integrates Gemini 3.7 Flash and DeepSeek V4 Flash/Pro directly into the editor. While VS Code maintains an ecosystem of over 100,000 plugins, Zed targets performance through its custom GPUI framework. This framework renders every pixel natively via Metal on macOS or DirectX on Windows, eliminating the abstraction layers found in Electron. You might find the smaller extension library a hurdle if your workflow relies on niche tools. The integration of Claude Code and Gemini CLI via the Agent Client Protocol provides high-speed AI interaction. Zed also supports GitHub Copilot and allows users to use their own API keys for various models. The speed of the editor helps mitigate the latency seen in Electron-based alternatives, making it a strong choice for developers who manage heavy MCP workflows.

Share

Technewsdaily

Senior tech writer covering AI, gadgets and cybersecurity. Breaking down the news that matters, every day.