Zed Problems & Issues
Real user-reported problems, complaints, and limitations for Zed. Based on analysis of 13 signals.
Overall score: 72/100
Issues by Category
Zed extensions: why is the library so small?
Zed supports language, theme and tool extensions, but the library is far smaller than the VS Code marketplace and VS Code extensions do not carry over. Users report missing tools such as git graph or language-specific extras.
Zed debugger and remote development less polished than VS Code
Zed has a debugger and SSH remoting, but 2024 to 2026 accounts say breakpoint UX has rough edges, and remote debugging and extensions on the remote host were weaker than VS Code's mature tooling.
Zed AI agent less polished than Cursor
Reviewers describe Zed's agent as capable but less refined than Cursor's, with no proprietary coding model. You can bring your own API keys for Anthropic, OpenAI, Google and others.
Zed git integration is less mature than GitLens
Git works for daily commits and has a visual graph, but reviewers say it lacks the depth of GitLens and other VS Code git extensions.
Zed not working on Linux: Vulkan and GPU errors
Zed renders through Vulkan on Linux. Official docs list NoSupportedDeviceFound, ERROR_INITIALIZATION_FAILED and GPU Crashed errors, plus AMD Broken Pipe with amdvlk, and hybrid laptops picking the wrong GPU.
Zed blank or invisible window on Linux and WSL
GitHub issues describe Zed opening an empty or invisible window on Linux, especially on Wayland and WSL2. Forcing X11 by clearing WAYLAND_DISPLAY is the common workaround.
Zed on Windows: later and rougher than macOS
The Windows port lagged macOS and Linux because of platform differences (file operations, paths, GPU memory with separate VRAM, WSL handling). Zed 1.0 lists Windows as stable, but users still post Windows-specific problems such as C# extension highlighting.
Zed Max tokens reached error in the agent panel
Long agent threads hit model token limits and stop with a Max tokens reached error. Starting a new thread or switching model is the documented fix.
Is Zed Pro worth it? $10/month with only $5 of tokens
Pro costs $10/month with $5 of included tokens, and hosted usage beyond that is billed at API list price plus 10%. Heavy agent users can pay well over $10, though a spend limit can cap it.
Zed AI usage stops when the spend limit is reached
Once the monthly spend limit is hit, hosted model usage stops until it resets, and failed threshold invoices ($10 steps) also block hosted models. Docs across channels describe the trial and credit amounts differently, which confuses buyers.
Why is Zed using 100% CPU or freezing?
Reports include 100% CPU after resuming from sleep on Linux X11 with NVIDIA GPUs, idle message-loop CPU use on Windows and fullscreen freezes in KDE. Some are partially fixed in later releases.
Migrating from VS Code to Zed: settings and keymaps
Zed uses its own JSON settings and keymap format; VS Code settings and extensions must be recreated manually. It has a VS Code keymap option and Vim and Helix modes.
Zed language support gaps: C#, Vue and niche languages
Users report autocomplete or highlighting problems for some languages (C# via a community extension, Vue with Stylus). Support often depends on a community extension and language server.
Regret Patterns
Common reasons users regret choosing Zed.
Missing an extension you depended on
VS Code extensions do not carry over.
Surprise AI bill
Usage beyond the $5 credit is metered.
Linux graphics issues
Vulkan or Wayland problems block use.
Language support gaps
A language server or community extension is flaky.
Remote or debugging weaker than expected
Switch back for a complex remote setup.
Settings must be rebuilt
No import of VS Code settings.
When Zed Breaks Down
Specific scenarios where Zed fails or underperforms.
Linux without a Vulkan GPU
Zed cannot start rendering, for example in some VMs or on ARM Linux hardware.
Wayland with hybrid GPUs
Wrong GPU or blank window until you set DRI_PRIME or force X11.
Large monorepo on low inotify limits
Too many open files errors until you raise limits.
Heavy agent sessions
Spend limit reached and hosted usage stops.
Niche language stack
Missing extension or weak language server.
Remote debugging
Rough breakpoints and limited remote extension support.