· editors / zed / vscode

Zed in 2026: Has the Editor Finally Matured?

Zed 1.0 shipped with SSH remoting, a native git panel, a debugger, and first-class AI agents. The extension gap (800 vs 50,000) is still the honest reason most developers won't switch from VS Code today.

By

1,452 words · 8 min read

Pick Zed if you’re on Apple Silicon or a modern Linux box, care about editing feel, and can live with ~800 extensions instead of 50,000. Stay on VS Code if your workflow depends on a database explorer, an API client, or any niche extension that hasn’t been ported. Zed 1.0 shipped April 29, 2026 with a real feature set — SSH remoting, a native git panel, a debugger, and first-class AI agent support — but it is still a performance-first editor that trades ecosystem breadth for speed and polish.

Who this is for

Developers on M-series Macs or modern Linux who want a fast, low-overhead editor with strong AI agent integration and are not dependent on the long tail of VS Code extensions. If your daily workflow runs through database panels, REST clients, or cloud-service sidebars, stop here — those gaps are real.

What we tested

Zed: v1.3.6 stable (released May 21, 2026)
VS Code: comparison figures from published benchmarks

Performance data comes from devtoolreviews.com and tech-insider.org benchmarks; not independently re-run. All other findings (AI features, git, remoting, stability) are sourced from Zed’s official blog, docs, and GitHub issue tracker as of May 29, 2026.

Performance

Zed’s performance lead over VS Code is real and large in 2026.

MetricZed v1.3.xVS Code (moderate extensions)
Cold startup~0.4 s~3.0 s
RAM at idle~180–222 MB~650 MB
Input latency (keystroke→screen)~2 ms~12–25 ms
Large-file open (50 MB)~0.8 s~3.2 s

The gap comes from architecture: Rust plus a custom GPU-accelerated UI framework (GPUI) instead of Electron. VS Code with a folder open spawns 23+ processes; Zed uses roughly 5.

“Blazing-fast” is a banned phrase in this publication, so here’s the concrete version: 7.5× faster cold start, 3.6× lower RAM, and 6–12× lower input latency. The input latency difference in particular is physical — you feel it rather than measure it.

Linux had a significant graphics-backend instability issue that was resolved in v0.225.9 (February 25, 2026) when the backend switched to wgpu. Apple Silicon has been the headline use case throughout Zed’s history; Linux is now a reliable second platform.

Extension ecosystem

This is the clearest gap and the most honest reason not to switch.

  • Zed: ~800 extensions (WASM-based, sandboxed — extensions cannot crash the editor)
  • VS Code: ~50,000 extensions

Coverage is solid for mainstream languages — TypeScript, Python, Rust, Go, Java, PHP, Ruby all have language servers. Themes and icon sets are well represented. The most-downloaded extension is “HTML support” at 5.5M installs, which gives you a sense of what developers are actually reaching for.

What’s missing as of May 2026: database explorers, API testing clients (no REST Client equivalent), cloud-service integration panels (AWS/Azure), advanced Docker management, and long-tail language-specific linters that exist only as VS Code extensions.

The sandboxing model is a genuine architectural win — a badly behaved Zed extension cannot lock up the editor. But 800 vs. 50,000 is not a gap you close in a year. Extensions are where most developers will either find Zed workable or won’t.

AI integration

Zed has made the most aggressive AI bets of any native editor in 2026.

Autocomplete tier (edit predictions): Powered by Zed’s Zeta model (v2.1, May 8 2026 — 3× fewer tokens, 50ms faster response time according to Zed’s changelog). Free tier: 2,000 accepted predictions per month. Zed Pro: $10/month. Bring-your-own-key: unlimited predictions.

Agent tier: Via the Agent Client Protocol (ACP), Zed runs Claude Agent, Codex CLI, Gemini CLI, and GitHub Copilot as first-class sidebar agents. Terminal Threads (May 20, 2026) lets you run Claude Code or Amp as persistent sidebar threads — a meaningful UX step up from jumping between terminal sessions. ChatGPT subscription integration arrived May 15, 2026.

AI features work in remote SSH sessions. That’s not a given for AI-augmented editors, and it matters if your development environment lives on a remote machine.

Where Zed trails Cursor: Zed lacks codebase-wide semantic indexing and built-in multi-file agentic editing. ACP agents (Claude Agent, etc.) can do multi-file work through their own context management, but Zed doesn’t build a project-level index the way Cursor’s Composer does. For developers whose primary workflow is “AI edits files across the whole repo,” Cursor is still the better tool.

Pricing perspective: Zed AI at $10/month is half of Cursor Pro ($20/month). If the ACP model (bring your own agent subscription) covers your workflow, that’s a meaningful cost difference.

Remote development

SSH remote development (announced October 2024) is in active production use. The architecture is clean: Zed UI runs locally, language servers, terminals, and tasks run on the remote machine, connected via SSH ControlMaster multiplexing.

What works reliably: language servers persist across connection drops (the daemon reconnects automatically), AI features work in remote sessions, port forwarding is supported, and collaboration with remote projects is transparent to collaborators.

Known limitations from the official docs:

  • Does not handle very large directories well over SSH
  • Cannot open remote files by typing zed <path> in the remote terminal
  • Windows cannot act as an SSH server (client only)
  • Requires Zed v0.159+ on both sides

For the common case — SSH into a Linux server for development — this is production-ready. For complex multi-container setups or VS Code Remote Containers workflows, the parity isn’t there yet.

Git

Native git support landed March 2025. A community sprint across November–December 2025 delivered 66 improvements: 5 major features, 28 bug fixes, 33 smaller improvements. The February 2026 blog post documenting the sprint shows genuine community investment, not just checkbox shipping.

Current feature set (v1.3.x): inline blame, gutter indicators, project diff with editable hunks, file history with commit browser, per-hunk and per-file staging, commit with undo, branch create/switch/delete, stashing, push/pull/fetch, merge conflict resolution, AI-generated commit messages, and permalinks.

Missing vs. GitLens: interactive rebase UI, code-lens annotations above every line, heat-map blame visualizations, the full repository explorer panel, history-graph views.

Bottom line: Zed’s built-in git is a viable daily driver for standard feature-branch work. If your workflow involves regular git archaeology — bisecting across hundreds of commits, annotated heat maps, interactive rebase — GitLens in VS Code is still the reference.

Stability

Rapid release cadence (multiple stable releases per week) means bugs get fixed fast, but regressions appear regularly.

Notable events:

  • February 2025: Reports of CPU saturation and Python LSP breakage on older hardware (2019 MacBook Pro). Acknowledged and addressed by the Zed team.
  • February 12, 2026 — Issue #49005 (P1, “frequency:common”): A RefCell already borrowed panic in GPUI’s app core caused frequent crashes across all platforms. Fixed in PR #49086 within the same release cycle.
  • v0.225.9 (February 25, 2026): Linux graphics backend replaced with wgpu, resolving a class of GPU stability issues.

As of late May 2026: ~2,500 open GitHub issues. The crash rate has improved materially since the RefCell fix and the Linux wgpu migration. Residual reports of editor freezes under specific conditions (large directory loads, certain LSP operations) exist but are not the common case.

Platform maturity order: macOS > Linux > Windows. Windows support arrived October 2025. Independent reviews describe it as stable in 2026, though the feature gap vs. macOS remains.

Verdict

Zed 1.0 has closed the major gaps that made it a hobbyist pick two years ago. It now has git, SSH remoting, a debugger, Windows support, and serious AI agent integration. The extension ecosystem (800 vs. 50,000) remains the honest reason most developers will not switch from VS Code today.

Use Zed if: you’re on Apple Silicon or modern Linux, care about editing feel and input responsiveness, want first-class AI agent support, and can confirm your required extensions exist in the registry.

Stay on VS Code if: your workflow depends on specific extensions with no Zed equivalent, you need Cursor-style codebase-wide AI indexing, or you do complex git history work and rely on GitLens.

References