Zed 1.0

· devtools ai-agents coding · Source ↗

TLDR

  • Zed declares 1.0 after five years building a GPU-accelerated, Rust-native editor on their own GPUI framework, replacing the Electron/browser-engine approach.

Key Takeaways

  • GPUI renders the entire UI via shaders on the GPU, the same architecture used in game engines, giving Zed performance headroom no Electron-based editor can match.
  • Zed supports parallel AI agents natively, an Agent Client Protocol connecting Claude Agent, Codex, OpenCode, and Cursor, built into the editor’s core rather than bolted on.
  • DeltaDB, a CRDT-based synchronization engine with character-level change tracking, is in active development to let humans and agents share a live, consistent view of a codebase.
  • Zed for Business ships with centralized billing, role-based access controls, and team management, targeting engineering org rollouts.
  • 1.0 covers Mac, Windows, and Linux, Git integration, SSH remoting, a debugger, and exceeds one million lines of code across five years.

Hacker News Comment Review

  • The most consistent friction point among switchers is the search UX: Zed opens results in a new tab rather than an inline panel, with no sidebar option, and commenters switching between Zed and VS Code or Neovim cite this as the reason they cycle back.
  • Several commenters flagged a broad data-processing clause in the Zed for Business license agreement, raising questions about what customer code Zed can store, transmit, and create derivative works from.
  • Daily-driver praise centers on the SSH remote workflow as a first-class feature, with users pairing Zed with cloud dev environments and noting the terminal, agents, and file editor unified in one pane as the practical differentiator from JetBrains IDEs.

Notable Comments

  • @jorgeleo: Section 4.1 of the Zed Business license grants Zed rights to “use, copy, store, disclose, transmit, transfer, display, modify, create derivative works from” customer data.
  • @Meekro: Legacy PHP codebases with pre-2020 conventions surface an “ocean of red” warnings in Zed, and disabling them per-rule is not trivial.
  • @inickt: Proposes swapping Alacritty for libghostty as the terminal backend, noting architectural alignment between Ghostty and GPUI’s approach.

Original | Discuss on HN