Zed

Zed is a from-scratch code editor written in Rust by Nathan Sobo and the team behind Atom and Tree-sitter. It is built on a custom GPU-accelerated UI framework (GPUI), uses CRDTs for true multiplayer editing, and runs at near-native latency even on large repos — opening the same project that VS Code takes seconds to chew through in well under a second. The original pitch was "the editor for fast humans"; in the AI era, Zed has become an equally serious AI editor. It ships first-class Anthropic, OpenAI, Google, and local-model integrations, an in-editor agent panel that can read and edit files, run terminal commands, and reason across the codebase, plus full Model Context Protocol (MCP) support so any MCP server (GitHub, Linear, Postgres, custom) becomes a tool inside the agent. Multiplayer means a human and an agent — or two humans and an agent — can collaborate on the same buffer in real time. The editor is free and open-source for individual use under a permissive license, with paid plans for hosted AI usage and a team plan with admin controls. Best fit for engineers who care about latency, want a single editor that does multiplayer + AI natively, and are invested in MCP as the agent tool standard.

For a realistic evaluation, install Zed beside your current editor rather than replacing the existing setup on day one. Use the same repository for at least one working week and measure cold-start time, search latency, memory use, extension gaps, and how often the AI agent produces a patch you can accept without repair. Run at least 20 representative agent tasks: small refactors, test generation, unfamiliar-code explanations, and a few changes spanning multiple files. Record completion time and correction count. Raw generation speed matters less than the percentage of changes that survive tests and review.

Zed's collaboration model is a meaningful differentiator when remote pairing is common. Test an actual session with two engineers, including follow mode, shared navigation, and a handoff during an active edit. For MCP, connect only a low-risk server first and verify tool permissions, credential storage, confirmation behavior, and logs before exposing issue trackers, source control, or production data. An MCP connection increases reach, but it also increases the damage a mistaken or malicious instruction could cause.

Pricing requires a direct check before purchase because the live vendor pages were unreachable during this scheduled run. The repository record lists a free editor option plus paid hosted-AI and organizational tiers, but current prices, included model usage, overages, and enterprise controls were not independently verified. Teams should compare total monthly cost at expected prompt volume, including external model API charges when bringing their own keys.

The strongest fit is a developer who values responsiveness, native collaboration, and an integrated agent workflow more than a huge extension catalog. The weaker fit is a team dependent on VS Code-only extensions, mature remote-development workflows, or centrally mandated IDE controls that Zed has not demonstrated in a pilot. Keep the incumbent editor available until language tooling, debugging, containers, accessibility, and required extensions all pass a written checklist.