Why Zed?#
Zed is a newer editor (written in Rust, by some of the people who built Atom) that competes with VS Code on speed and a leaner footprint. The specific things that make it worth trying:
- Speed. Cold start and large-file rendering are noticeably faster than VS Code.
- Built-in features over extensions. Most of what VS Code expects you to install (LSP, Git panel, multi-cursor, terminal) ships in-box.
- Real-time collaboration. Shared sessions with multi-cursor editing, similar to Google Docs but for code.
- Minimal UI. Less chrome, more code on screen.
- Native Git support. Diff view, stage/commit, and inline blame work without an extension.
- Lower memory footprint. Several hundred MB lighter than VS Code on a comparable project.
This guide covers:
- Installing Zed with Homebrew.
- Configuring it to feel close to VS Code for someone switching over.
- Tips for using AI tools alongside it.
Installing Zed with Homebrew#
Zed runs on macOS and Linux. On macOS the fastest install is Homebrew. If Homebrew isn’t set up, the official site has the install command.
Install Zed:
brew install zedLaunch it on the current directory:
zed .Extensions and configuration for a VS Code-like setup#
Zed doesn’t rely on traditional extensions like VS Code but comes with built-in capabilities that cater to most developers’ needs. However, tweaking Zed to match your workflow is key. Here are some tips:
1. Language support#
Zed supports a variety of programming languages out of the box, but for more advanced tooling:
- Check the Zed Docs for supported languages and how to enable additional tooling if needed.
- Integrate external LSPs (Language Server Protocols) to boost autocomplete and error detection.
2. Git integration#
Enable Git integration by:
- Settings Made Simple: Navigate to Settings and ensure Git features are toggled on for seamless version control.
- Integrated Workflow: Use the built-in Git panel to stage, commit, push, and even resolve conflicts, all without needing to leave Zed.
- Speedy Diff Views: Quickly view diffs inline and roll back changes with minimal hassle.
- Built-In Merge Tools: Simplify merge conflict resolutions with Zed’s intuitive interface.
With these features, Git integration in Zed ensures a developer-friendly experience for teams and solo devs alike.
3. Keyboard shortcuts#
Customize your keyboard shortcuts in ~/.zed/settings.json:
{
"keybindings": {
"Ctrl+Shift+P": "command-palette",
"Cmd+S": "save-all"
}
}This gives you a VS Code-esque feel for common commands.
4. Themes and UI tweaks#
Zed ships with a sleek dark mode, but you can tweak the editor’s appearance:
- Open
~/.zed/settings.jsonand modify theme settings. - Experiment with font sizes and line heights for optimal readability.
- For a VS Code-like experience, align font families and enable line numbers for a familiar coding environment.
5. Terminal integration#
Zed doesn’t have a built-in terminal, but you can:
- Use your system’s terminal alongside Zed for commands and scripts.
- Set up shortcuts to quickly switch between Zed and terminal windows.
6. Snippets and Code templates#
Automate repetitive code patterns by creating reusable snippets:
- Define custom snippets in the settings file.
- Use AI tools like Tabby or Copilot to auto-generate boilerplate code.
Tips and tricks for using AI with Zed#
Zed has shipped an in-editor AI assistant in newer versions, but you may still want to integrate external tools. A few patterns that work:
1. Copilot integration#
To use GitHub Copilot:
- Ensure you have the Copilot CLI installed and configured.
- Use terminal-based workflows alongside Zed for generating code snippets.
2. ChatGPT or local models#
For quick AI-driven help:
- Pair Zed with a browser-based AI like ChatGPT.
- Use tools like Tabby or Cursor for AI-assisted local code completion.
3. AI-assisted debugging#
When debugging:
- Use AI to explain error messages or suggest fixes.
- Copy relevant code blocks into an AI prompt for targeted help. Be mindful of sensitive data.
4. Writing regex or shell commands#
Need a gnarly regex or a precise shell command? AI tools excel at generating these. Write prompts like:
“Write a regex to extract email addresses from a text file.”
“What’s the bash command to recursively find all
.txtfiles in a directory?”
Workflow tips: from VS Code to Zed#
Transitioning from VS Code? Here’s how to smooth the process:
- Sync Settings: Export your most-used VS Code settings and apply similar configurations in Zed.
- Use Zed’s Collaboration Features: Invite a pair programmer and enjoy real-time edits.
- Embrace Minimalism: Zed’s lightweight approach can help you focus on coding, not tweaking.
Closing notes#
Zed is worth a serious look if VS Code feels heavier than the work calls for, or if you spend a lot of time pair-programming and want collaboration as a first-class feature instead of an extension. The migration cost is low: install it, point it at a project, see how the first hour feels.
