Zed AI

AI integration and user experience

• Many users praise Zed’s assistant panel, inline edits, and new /workflow feature for fast, diff-based code transformations directly in the editor.
• Others find the AI UX clunky in places (e.g., selection behavior, missing side‑by‑side diffs) or prefer simple autocomplete over chat/agents.
• Some like that AI features can be disabled via config, but others want build-time options to strip AI entirely and worry “off” doesn’t guarantee no data upload.

Cloud vs local AI, performance, and hardware

• Debate over local/offline autocomplete: JetBrains’ small local models show it’s possible but limited; some see local as essential for privacy, others say latency/quality make small local models not worth it yet.
• Concerns about laptop battery and CPU/GPU load when running local LLMs.
• Zed can use multiple providers (Anthropic, OpenAI, Gemini, Ollama), which some appreciate as modular and Unix-like.

Privacy, security, and workplace constraints

• Strong worries about sending proprietary code to third‑party clouds, often incompatible with employer policies.
• Some want explicit “privacy modes” and clear statements that code isn’t stored; they note Cursor advertises this more clearly.
• Preference from some to connect Zed directly to an LLM provider to minimize intermediaries.

Comparisons: Zed vs Cursor, VSCode, JetBrains, Neovim, etc.

• Cursor is repeatedly cited as having superior “modify existing code” workflows, shadow workspaces, and very strong inline suggestions.
• Zed is praised for being native, fast, open source, and smoother than Electron-based editors, but some report basic bugs and missing language features that push them back to Neovim/VSCode.
• Some users value Zed’s transparent prompts and hackable slash commands vs. Cursor’s opaque “magic.”

Editor fundamentals and monetization

• Several comments wish Zed would prioritize core editor robustness, language support, and basic UX over AI and collaboration.
• There’s demand for a “fast, programmable, native GUI” editor with rich extensibility, and skepticism that VC-funded tools can avoid AI-heavy monetization.
• Others welcome AI subscriptions as a viable business model that keeps the core editor open-source.

Impact on learning and code understanding

• Split views on AI’s effect on juniors: some see it as an empowering tutor; others fear overreliance, poorer PR quality, and slower skill growth.
• Multiple people want AI that helps understand why code exists and how systems evolved (commits, tickets, invariants), not just what code does or how to write more.