Zed
zed.dev- Category
- Developer Tools
- Rank
- No. 12Tools index
- Listed in
- #14 Interface with your agents
- Pricing
- Freemium
- Type
- TOOL
- Builder
- zed-industries
- GitHub
- 89.9k stars
- Latest release
- v1.19.1-pre
- Date
About
Multiplayer code editor written in Rust. GPU-rendered, AI-native, designed for raw speed.
What it does
Zed is a desktop code editor from Zed Industries, written in Rust on its own in-house interface framework, with app state updated on a single thread. One codebase carries far more than editing: a collaboration server, a headless server for editing over SSH, a REPL, debugger support, Vim mode, an extension host, and built-in connectors for nine AI model providers including Anthropic, OpenAI and Ollama. A small companion shell command opens files by talking to the already-running app rather than doing any editing itself.
Why it's ranked here
Active development, a genuine open-source license, and unusual candor about mechanism make this a strong pick. The license is a real OSI license rather than source-available, and the company publishes its funding model openly. Performance is instrumented rather than marketed: a stated frame budget, documented profiling workflows, and an explicit split of what runs locally versus remotely all live in the repository. It delivers native-speed editing with language servers, debugging, remote SSH work and several model providers in one binary instead of wrapping an existing editor. The large open-issue backlog is the visible cost of that scope.
What's good
The speed claim is backed by tooling, not assertion: the docs describe tracing and flamechart workflows, separate profilers for the foreground and background executors, and a one-line timer that warns when a call runs long, and the contribution checklist holds every frame to a hard 8ms budget. The remote-development docs are unusually precise about what runs where: the interface, syntax parsing and model calls stay local while language servers, tasks and the terminal run on the remote host, with port forwarding and a path for uploading the server binary to hosts that have no internet access.
Tradeoffs
The primary license is GPL-3.0-or-later, which matters to anyone hoping to embed the interface framework or ship a modified commercial fork. Building from source is a commitment: 249 workspace members on a recent Rust edition, and the setup docs immediately hand off to three platform-specific guides. Re-entrant state updates fail at runtime rather than at compile time. There is no web build, and Windows works as a client but cannot act as a remote host. Contribution has friction by design: a contributor license agreement, a cap of three open pull requests per author, and a stated merge rate of roughly half of submitted changes.
How to use it well
Install a prebuilt release or use a package manager; compiling the workspace is not a prerequisite to evaluating it. Lean on the companion shell command, which can open a file at a line and column, force a new window, wait for a file to close, and diff two directories by pairing files on their relative paths. For remote work, define connections in settings and enable upload over SSH when the host has restricted internet. Extend through extensions rather than patches: languages, themes, icon themes, debugger adapters, snippets and MCP servers are all supported, and new languages or themes will not be merged into core.
Technical notes+
The Cargo workspace declares 249 members, 243 under the crates directory, with default-members limited to the zed crate; separate provider crates cover Anthropic, OpenAI, Ollama, LM Studio, Bedrock, Copilot, DeepSeek, Mistral and OpenRouter. The UI framework is the in-repo GPUI: crates/gpui/src/app.rs holds app state in an Rc<AppCell>, a RefCell wrapper with foreground and background executors attached, so updates are single-threaded and re-entrancy surfaces as a runtime borrow error; a comment there describes the wrapper as a temporary construct kept around to debug double borrows. crates/zed/src/main.rs runs a sandbox-launcher check before argument parsing, refuses to run as root on unix, and can act as an askpass responder, a minidump crash server, or an ETW trace recorder instead of an editor. The shell command in crates/cli/src/main.rs talks to the running app over an IPC one-shot server and implements a diff mode that walks two directories, pairs files by relative path, and stubs in empty files for one-sided entries. crates/remote_server/src/server.rs exposes run, proxy and version subcommands over unix sockets and forwards telemetry to the client. docs/src/performance.md documents Tracy tracing, samply flamecharts and per-executor profiling; CONTRIBUTING.md states the 8ms frame budget. Tests sit beside the code as cfg(test) modules rather than in a central test directory.
Observed
- License
- GPL-3.0-or-later primarily, with Apache-2.0 components where marked
- Language
- Rust
- Workspace structure
- 249 workspace members, 243 of them under the crates directory; the default build target is the editor crate alone
- Remote host platforms
- Remote server runs on macOS and Linux only; Windows is supported as a client but not as a remote host
- Web build
- Not available
Read from README.md, Cargo.toml, crates/zed/src/main.rs, crates/gpui/src/app.rs, crates/remote_server/src/server.rs, docs/src/development.md, docs/src/performance.md, docs/src/extensions.md, CONTRIBUTING.md, crates/cli/src/main.rs, docs/src/remote-development.md.
Intel on Zed
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.