The archive · Product Ideas · Technical decision · 2017–2026
Zed 1.0: a code editor rebuilt like a video game — Rust, GPU shaders, CRDT multiplayer
Atom's founders rebuilt the editor in Rust with GPU shaders and built-in CRDT multiplayer — 1.0 ships after five years, a million lines, and parallel AI agents.
Zed Industries
What it had to solve
Atom's creators hit a ceiling: Electron made an editor easy to ship but impossible to make feel great. In 2017 Nathan Sobo wrote 'we have to start over'; four years later the same team founded Zed to rebuild the editor from first principles.
How it works
Zed began as a refusal: in 2017 Nathan Sobo, who had built GitHub's Atom editor, wrote in his journal that the team 'has to start over.' Atom ran on Electron, web technology that made an editor easy to ship but imposed a ceiling — memory, garbage collector pauses and DOM rendering that no amount of polishing could remove. The fix, he concluded, was to own the foundation.
So Zed was built like a video game instead of a web page: the whole application feeds data to shaders on the GPU, rendered by GPUI, a UI framework written from scratch in Rust. CRDTs put real-time collaboration into the text data model itself, and the team owned every layer from tree-sitter parsing to rendering — the opposite of Atom's approach.
When Zed 1.0 shipped on April 29, 2026, after five years of development and more than a million lines of code, it was also AI-native: keystroke-level edit prediction, parallel agents in one window, and an open Agent Client Protocol that lets Claude Code, Codex, OpenCode and Cursor work inside it. 'We built AI into our editor's foundation instead of bolting it on top,' the team wrote.
Hundreds of thousands of developers now use Zed daily across macOS, Windows and Linux. The 1.0 release also introduced Zed for Business for organizations, and the roadmap points to DeltaDB, a CRDT-based sync engine tracking every edit at character level so humans and AI agents share one consistent view of the codebase.
Why it lands
- Web technology made Atom easy to ship but set a hard ceiling on feel; the only fix was owning the foundation.
- Rendering with GPU shaders instead of DOM made fast typing and UI an architectural consequence, not an optimization.
- CRDTs put real-time collaboration into the data model, so multiplayer was native rather than an add-on.
- Building AI into the foundation — edit prediction, parallel agents, an open agent protocol — made the editor a neutral home for third-party agents.
What it did
Zed 1.0 (April 29, 2026) reached hundreds of thousands of daily developers and launched Zed for Business at $30 per user per month. The release validated the contrarian architecture — native Rust, GPU rendering, CRDT sync — as the editor market chased native, AI-first tools.
What you can take
When the platform caps your product's feel, rebuilding the foundation is a product decision, not just engineering — owning the whole stack is what lets you ship what nobody else can.
Since then
Zed 1.0 shipped April 29, 2026 after roughly five years of development, with over a million lines of code and hundreds of thousands of daily users. The release came with Zed for Business (centralized billing, role-based access, team management) and the team kept shipping weekly. On the roadmap is DeltaDB, a CRDT-based synchronization engine that tracks every change at character-level granularity so humans and AI agents share a single consistent view of the codebase; the Agent Client Protocol already connects Claude Code, Codex, OpenCode and Cursor to the editor.
Sources
- Zed is 1.0
- We Have to Start Over: From Atom to Zed
- 5年間の開発を経て「Zed 1.0」がリリース、Rust/GPUで速度と応答性を極めたコードエディター
spotted an error? The archive wants to know.
Your turn
You just read one. Describe the brief you are staring at, and see who has been given the same problem.
Free account · 3 free questions · no card