Zed

Zed#

Zed is a modern, GPU-accelerated editor written in Rust by the team behind Atom. Designed for speed, multiplayer-by-default, and tight AI integration. Cross-platform on macOS / Linux / Windows; fully open-source as of 2024.

Distinctive Features#

What Zed brings that the rest of the modern editor field doesn’t. GPU rendering is the most-quoted differentiator; the multiplayer features and the AI-as-a-first-class-citizen design are the other two pillars.

  • Native GPU rendering, not Electron; instant typing latency on a modern machine.

  • Multiplayer, collaborative editing built into the editor; share a project with a teammate over a peer-to-peer connection.

  • Built-in AI, chat, inline edits, agentic mode; bring your own Claude / OpenAI / Ollama / Mistral / OpenRouter key.

  • First-class LSP, Tree-sitter, DAP.

  • Vim mode built in (no extension needed).

  • Channels, voice + screen + collaborative editor sessions.

  • Git integration, inline diff, blame, hunk staging.

  • Tasks system, runnables defined per project.

Files#

Configuration is JSON and hot-reloads as you save; the editor picks up changes without a restart. Per-user settings live under the XDG config directory; per-project overrides go in .zed/ inside the repo.

  • ~/.config/zed/settings.json, main config.

  • ~/.config/zed/keymap.json, keymaps.

  • Per-project .zed/settings.json.

JSON-based, with hot reload as you edit.

The Speed Story#

Zed renders the editor surface on the GPU and does almost everything off the main thread. The result: typing latency, scroll, and search are faster than every Electron editor and most native editors. On large files (tens of MB) Zed remains responsive where Atom and VS Code stutter.

AI Integration#

Zed’s “Assistant” panel sits alongside the editor and supports multiple model providers behind one interface. Bring-your-own-key keeps cost and privacy in the operator’s hands; system prompts can be customized per project to keep the assistant on script:

  • Models from OpenAI, Anthropic, Google, OpenRouter, and Ollama (local).

  • Inline edits via Ctrl-Enter on a selection.

  • Multi-file agentic changes.

  • “Slash commands” for built-in actions (file mention, diagnostics context, terminal output).

Customizable system prompts per project; bring-your-own-key to control cost and privacy.

Languages#

Most languages have first-class Tree-sitter and LSP support out of the box: Rust, Go, Python, TypeScript / JavaScript, C/C++, Ruby, Elixir, Zig, and many others. Less-common languages may need community-written extension packages.

Strengths#

What Zed wins on against the rest of the modern editor field. The speed and the open-source license are the structural advantages; multiplayer and bring-your-own-key AI are the unique features that no other major editor matches.

  • Fastest of the modern editors.

  • Multiplayer is unique and genuinely useful.

  • Open-source since 2024; Apache + GPL dual-licensed.

  • AI built-in, with bring-your-own-key.

  • Vim mode is solid for modal users.

  • No Electron, low memory footprint.

Weaknesses#

What Zed has not caught up on yet. The extension ecosystem is much smaller than VS Code’s, the non-macOS builds are newer, and the remote-development story still trails what Microsoft ships.

  • Smaller extension ecosystem than VS Code.

  • Newer, so some workflows / debuggers are less polished.

  • Linux / Windows builds are newer than macOS; macOS still feels most polished.

  • Remote development less mature than VS Code’s.

When to Pick Zed#

Pick Zed when speed, multiplayer, or bring-your-own-key AI matter to you and you can accept a smaller extension ecosystem. The open-source license and lack of telemetry are the other common reasons operators move from VS Code or Cursor.

  • You want a fast, native editor.

  • You collaborate live with teammates.

  • You like AI integration but want to control providers and keys.

  • You’re a Vim user who wants modal editing without a plugin.

  • You’re frustrated with Electron memory / battery costs.

Alternatives#

Other paths to similar goals. Each one trades something different: ecosystem depth, AI integration, license, or how much weight the editor carries on disk and in memory.

  • VS Code for the bigger extension ecosystem.

  • Cursor for deeper AI integration in a VS Code shell.

  • Sublime Text for a fast paid native editor with deep history.

  • Lapce, another Rust GPU-rendered editor; smaller community.

Contents