Zed shipped a major update to its debugger this week. The previous debugger was usable but limited; the new version covers more languages with better UI.
For Zed users who’d been switching to other editors specifically for debugging, this closes a meaningful gap.
What’s new
Multi-language support. The debugger now works for Rust, Go, Python, JavaScript/TypeScript, and Ruby. Previously, support varied. Now most major languages have first-class debugger support.
Inline variable display. When stopped at a breakpoint, variable values appear inline next to their declarations. Common in JetBrains and VS Code; previously absent in Zed. The addition makes debugging much more pleasant.
Better breakpoint UI. Conditional breakpoints, log points, and breakpoint groups all have refined UIs. Setting up complex debugging scenarios is easier.
Run configurations. Saved run configurations for debug sessions. Useful for projects with multiple debug entry points.
What’s still rough
Some niche languages. C++, Swift, and others have weaker support. Workable but not as polished as the major languages.
Remote debugging. Debugging code running on a different machine has gaps. SSH-based debug, container debug, etc. Coming but not yet smooth.
Debug tracing. Detailed trace recording (like Chrome’s profiler) doesn’t have an equivalent in Zed. Some debugging workflows still benefit from external tools.
Why this matters
Debugger quality is one of the dimensions where IDEs (JetBrains specifically) historically led editors. Cursor and VS Code closed some of this gap; Zed had been behind.
This release closes most of the gap. Zed’s debugger is now competitive with Cursor’s and most VS Code setups for major languages.
For users who’d been on Cursor or VS Code specifically because the debugger was better, this is the change that lets you reconsider.
A specific test
I tried the new debugger on a Rust project that had been debugger-painful in older Zed:
- Setting breakpoints: clean
- Stepping through code: smooth
- Inspecting variables: inline display works well
- Conditional breakpoints: easy to configure
- Restart and re-debug: fast
The experience matches my expectations from JetBrains-class debuggers. For a relatively young editor, this is impressive.
What this means for tool choice
Zed’s debugger improvement is the kind of thing that affects evaluation of Zed for serious work.
Pre-update: “Zed is great except the debugger is weak.”
Post-update: “Zed is great.” For debug-heavy workflows, this matters.
For users who were on the fence about Zed because of the debugger: this is the right time to re-evaluate.
For users on JetBrains specifically because of debugger quality: Zed is now closer to competitive. Whether to switch depends on other factors (IDE-specific features you use, ecosystem comfort).
A meta observation
Zed’s pace of improvement remains aggressive. The team ships meaningful updates regularly. Compared to other editors of similar age, this is unusual.
The 1.0 release earlier this year was a marker; the post-1.0 pace continues. Whether this continues for years matters for users committing to Zed.
For now, the trajectory is positive. The debugger update is one of several meaningful improvements in recent months.
Worth updating?
For Zed users who debug regularly: yes. The improvements are substantial.
For Zed users who don’t use the debugger often: minor. The update doesn’t change other parts of Zed.
For users on other editors curious about Zed: this is one less reason to stay away. Combined with Zed’s other strengths (speed, vim mode, AI integration), the case for evaluation gets stronger.
What’s coming
Based on Zed’s roadmap discussion:
- Continued debugger language coverage (more niche languages)
- Better remote debugging
- Performance profiling integration
- Memory debugging tools
These would extend Zed’s debugging story further. The current state is competitive; further improvements push the lead.
For now, the debugger update is the right kind of release: meaningful improvement to a feature users care about, polished UX, working across major languages.
