Zed AI mode review — the Rust-based editor takes a real swing at AI

Zed has been the “Rust-based editor everyone admires but few daily-drive” since launch. Mid-2025 changed that materially. On August 20, 2025 — twelve days after this article was first drafted — the r/ZedEditor “Zed Raises $32M to Build the Future of Collaborative Coding” thread (359 upvotes) announced a Series B led by Sequoia. Zed went from “small-team-funded passion project” to “well-capitalized challenger to VS Code.”

Three weeks earlier, in mid-July, I”d started using Zed as primary editor on a side project to test the AI integration claims. The honest assessment: Zed”s editor performance is genuinely better than VS Code (the original promise), the AI features are credible but narrower than Cursor”s, and the pricing model is in flux. Specifically, the September 24 “Zed”s Pricing Has Changed: LLM Usage Is Now Token-Based” thread (72 upvotes) — six weeks after this article — captured the next pricing iteration. The Zed team is figuring out the business model in public.

This is the working review from three weeks of daily use.

What Zed actually is (in 2025)

Zed is a Rust-native code editor built by the team behind Atom (post-GitHub-acquisition pivot). Design philosophy: editor performance and collaborative features as first-class, AI features layered on top. Open source (GPL); free editor; paid AI features.

The differentiators:

• Native performance. Genuinely fast. Cold start, file opens, large file scrolling — all noticeably better than VS Code, Cursor, or Windsurf.
• Built-in collaboration. Real-time pair programming without a plugin.
• Native debugger (shipped June 2025, r/ZedEditor 452 upvotes). No language-specific debugger setup needed for major languages.
• Multi-LLM AI integration — Claude, GPT, Gemini, custom endpoints via OpenAI-compatible API
• Claude Code integration — Zed bundles a Claude Code-compatible mode that uses your existing Claude subscription for free

What Zed AI mode actually does

The AI features:

1. Inline assistant. Cmd-K (Mac) opens a prompt for inline edits. Modifies code in-place. Like Cursor”s Cmd-K but in a native-Rust editor.

2. Agent panel. Side panel with chat-based AI interaction. Supports multiple LLM backends. Can read open files and project context.

3. Multi-file context (added through 2025). Drag files into the agent panel; reference @file syntax in prompts. Less polished than Cursor”s multi-file UX but functional.

4. Claude Code mode. Zed integrates with the Claude Code agent — run your Claude Code session in Zed”s built-in terminal, get inline edit suggestions, file operations sync to the editor. This is the path that gives you Claude Code productivity inside Zed”s superior editor.

5. Bring-your-own-key. Use your own OpenAI / Anthropic / Gemini API keys; pay direct API pricing. The free path for power users.

The September pricing pivot

The September 24 token-based pricing thread (72 upvotes) captures a meaningful shift:

“We”re moving Zed AI from prompt-based limits to token-based pricing. We still offer, and always plan to offer, multiple ways to use AI in Zed without paying us: using your own keys, or external agents like Claude Code, remains free.”

Top response (39 upvotes): “This is literally the first transparent LLM pricing thats easy to understand. Very fair and relatable.”

Compared to Cursor”s pricing controversy in mid-2025, Zed”s pricing transparency was notably better received. The team explicitly preserved the “bring your own key” and “use Claude Code directly” free paths — recognizing the community”s pricing-sensitivity and offering opt-out paths Cursor didn”t.

What Zed gets right

After three weeks of daily use:

1. Editor performance. This is real. Files open instantly; large repos navigate without lag; the editor itself never feels in the way.

2. Native debugger. Saves the per-language debugger config tax. Just works for Rust, Go, Python, TypeScript.

3. Real-time collaboration. When it”s relevant (pair programming, mob programming, code review sessions), it”s genuinely better than screen-sharing.

4. OSS provenance. GPL-licensed editor; the runtime you use is the code you can read. Compared to Cursor”s closed-source fork of VS Code, this is a real advantage for users who care.

5. Configurable LLM backend. No vendor lock-in for AI features. Use any model via OpenAI-compatible endpoint.

What Zed gets wrong (still)

1. Extension ecosystem is small. VS Code has 50,000+ extensions. Zed has hundreds. For niche languages, frameworks, or tooling, the extension gap is real.

2. Multi-file AI editing is less polished than Cursor. Cursor”s “edit across these 5 files coherently” works better than Zed”s equivalent.

3. AI inline suggestions latency. Cursor”s ghost-text inline suggestions are faster and more responsive than Zed”s. Real difference for engineers who rely on autocomplete-flow.

4. JetBrains-quality refactoring isn”t there. For language-specific deep refactors (Java in IntelliJ, Python in PyCharm), the dedicated IDEs still win.

5. Windows support shipped later. Zed for Windows didn”t reach general availability until October 2025 (r/ZedEditor 509 upvotes thread). Mac was always primary; Windows users felt second-class for a long time.

The “Is this what Zed want?” critique

The r/ZedEditor “Is this what Zed want?” thread (83 upvotes, August 28) captures the community concern post-Series B: as Zed raises VC money, will it stay focused on editor performance or chase AI-trend features? The thread top comment (paraphrased): “Please don”t let this become the slide into mediocrity like so many other cases after raising big rounds.”

This is the Zed-specific version of every VC-funded developer-tool concern in 2025. Cursor”s pricing controversy is the cautionary tale; Zed”s explicit preservation of free paths in the September pricing pivot is the response. The Zed team appears to be navigating it more thoughtfully than peers — but it”s still early.

Creator POV vs Reddit dissent

The broader 2025 AI-editor creator landscape doesn”t cover Zed intensively. The video-content gravity is around Claude Code, Cursor, and the agentic-workflow patterns. Zed is too niche for general-audience AI-coding content; the patterns transfer but the specific tool doesn”t get the airtime.

IDD”s “ADDICTED to Claude Code: Alternatives” video (Aug 4) mentions Zed in passing as an alternative path — specifically, Zed-with-Claude-Code-bundled-mode is a viable “Claude Code productivity inside a better editor than terminal” path. This is the right framing for engineers evaluating Zed.

IDD”s “5 Agent PATTERNS” video (Aug 25) emphasizes that the agent patterns transfer across editors. Zed-with-Claude-Code works; the productivity comes from the Claude Code agent loop, not the editor specifically.

bycloud”s “Chinese AI Lab Teaching Everyone How To Save Millions of Dollars” video (Jul 19) is adjacent context — the editor / IDE choice matters less than the cost-conscious model choice. Zed supports OpenRouter / cheap-tier models via OpenAI-compatible endpoint; the cost-savings story applies to Zed-with-DeepSeek as much as Claude Code.

The Reddit dissent splits productively:

The pro-Zed performance camp — vocal in r/ZedEditor. “Best editor I”ve used in years” recurring sentiment.

The “Zed isn”t feature-complete enough” camp — accurate for users with specific extension dependencies. Counter: the gap is narrowing; the editor performance gain compounds for daily work.

The “use Zed + Claude Code instead of Cursor” camp — gaining momentum through 2025. Pattern: editor for editing, Claude Code for agent loop, no vendor lock-in on either.

The “this is still niche” camp — accurate. Zed is real but small. For most teams the network effects favor VS Code-based tools.

What this means for working engineers in early August 2025

Three practical positions:

1. If editor performance matters to you (large repos, fast iteration), try Zed for a week. The performance gain is real. Three-week test is enough to know if you”ll stick.

2. If you”re Cursor-fatigued, evaluate Zed + Claude Code combo. Get Cursor-like productivity via Claude Code without the VS Code-fork dependency, with native-performance editing.

3. Don”t expect feature parity with Cursor or VS Code. The ecosystem is smaller. If your workflow depends on specific extensions, audit availability before committing.

The honest critique

What this review doesn”t cover:

• Linux support is solid. Mac primary, Windows in 2025, Linux competent. Cross-platform users have all three options.
• The pricing model will likely keep evolving. Token-based now; future iterations possible. Pricing changes are a structural risk for any AI-tools commitment.
• Team / enterprise features are immature compared to JetBrains or VS Code. Single-engineer use is great; team coordination tooling is thinner.

For most working engineers reading this in early August 2025: Zed is a credible Rust-native editor with respectable AI features and the cleanest “BYOK + free path” pricing position in the category. If editor performance matters more to you than ecosystem depth, it”s now genuinely worth the migration evaluation. If you”re VS Code-ecosystem-locked, the migration cost is real and the marginal gain may not justify it.

For the editor-decision context, see our Vim/Helix/JetBrains + Claude Code guide for the editor-agnostic Claude Code path and the Cursor alternatives piece for the broader AI-editor landscape.