1---
2title: How to Migrate from RustRover to Zed
3description: "Guide for migrating from RustRover to Zed, including settings and keybindings."
4---
5
6# How to Migrate from RustRover to Zed
7
8This guide covers keybindings, settings, and the differences you'll encounter as a Rust developer switching from RustRover.
9
10## Install Zed
11
12Zed is available on macOS, Windows, and Linux.
13
14For macOS, you can download it from zed.dev/download, or install via Homebrew:
15
16```sh
17brew install --cask zed
18```
19
20For Windows, download the installer from zed.dev/download, or install via winget:
21
22```sh
23winget install Zed.Zed
24```
25
26For most Linux users, the easiest way to install Zed is through our installation script:
27
28```sh
29curl -f https://zed.dev/install.sh | sh
30```
31
32After installation, you can launch Zed from your Applications folder (macOS), Start menu (Windows), or directly from the terminal using:
33`zed .`
34This opens the current directory in Zed.
35
36## Set Up the JetBrains Keymap
37
38If you're coming from RustRover, the fastest way to feel at home is to use the JetBrains keymap. During onboarding, you can select it as your base keymap. If you missed that step, you can change it anytime:
39
401. Open Settings with `Cmd+,` (macOS) or `Ctrl+,` (Linux/Windows)
412. Search for `Base Keymap`
423. Select `JetBrains`
43
44This maps familiar shortcuts like `Shift Shift` for Search Everywhere, `Cmd+O` for Go to Class, and `Cmd+Shift+A` for Find Action.
45
46## Set Up Editor Preferences
47
48You can configure most settings in the Settings Editor ({#kb zed::OpenSettings}). For advanced settings, run `zed: open settings file` from the Command Palette to edit your settings file directly.
49
50Settings RustRover users typically configure first:
51
52| Zed Setting | What it does |
53| ----------------------- | ------------------------------------------------------------------------------- |
54| `format_on_save` | Auto-format when saving. Set to `"on"` to enable (uses rustfmt by default). |
55| `soft_wrap` | Wrap long lines. Options: `"none"`, `"editor_width"`, `"preferred_line_length"` |
56| `preferred_line_length` | Column width for wrapping and rulers. Rust convention is 100. |
57| `inlay_hints` | Show type hints, parameter names, and chaining hints inline. |
58| `relative_line_numbers` | Useful if you're coming from IdeaVim. |
59
60Zed also supports per-project settings. Create a `.zed/settings.json` file in your project root to override global settings for that project.
61
62> **Tip:** If you're joining an existing project, check `format_on_save` before making your first commit. Otherwise you might accidentally reformat an entire file when you only meant to change one line.
63
64## Open or Create a Project
65
66After setup, press `Cmd+Shift+O` (with JetBrains keymap) to open a folder. This becomes your workspace in Zed.
67
68To start a new project, use Cargo from the terminal:
69
70```sh
71cargo new my_project
72cd my_project
73zed .
74```
75
76Or for a library:
77
78```sh
79cargo new --lib my_library
80```
81
82You can also launch Zed from the terminal inside any existing Cargo project with:
83`zed .`
84
85Once inside a project:
86
87- Use `Cmd+Shift+O` or `Cmd+E` to jump between files quickly (like RustRover's "Recent Files")
88- Use `Cmd+Shift+A` or `Shift Shift` to open the Command Palette (like RustRover's "Search Everywhere")
89- Use `Cmd+O` to search for symbols (like RustRover's "Go to Symbol")
90
91Open buffers appear as tabs across the top. The Project Panel shows your file tree and Git status. Toggle it with `Cmd+1` (just like RustRover's Project tool window).
92
93## Differences in Keybindings
94
95If you chose the JetBrains keymap during onboarding, most of your shortcuts should already feel familiar. Here's a quick reference for how Zed compares to RustRover.
96
97### Common Shared Keybindings
98
99| Action | Shortcut |
100| ----------------------------- | ----------------------- |
101| Search Everywhere | `Shift Shift` |
102| Find Action / Command Palette | `Cmd + Shift + A` |
103| Go to File | `Cmd + Shift + O` |
104| Go to Symbol | `Cmd + O` |
105| Recent Files | `Cmd + E` |
106| Go to Definition | `Cmd + B` |
107| Find Usages | `Alt + F7` |
108| Rename Symbol | `Shift + F6` |
109| Reformat Code | `Cmd + Alt + L` |
110| Toggle Project Panel | `Cmd + 1` |
111| Toggle Terminal | `Alt + F12` |
112| Duplicate Line | `Cmd + D` |
113| Delete Line | `Cmd + Backspace` |
114| Move Line Up/Down | `Shift + Alt + Up/Down` |
115| Expand/Shrink Selection | `Alt + Up/Down` |
116| Comment Line | `Cmd + /` |
117| Go Back / Forward | `Cmd + [` / `Cmd + ]` |
118| Toggle Breakpoint | `Ctrl + F8` |
119
120### Different Keybindings (RustRover → Zed)
121
122| Action | RustRover | Zed (JetBrains keymap) |
123| ---------------------- | ----------- | ------------------------ |
124| File Structure | `Cmd + F12` | `Cmd + F12` (outline) |
125| Navigate to Next Error | `F2` | `F2` |
126| Run | `Ctrl + R` | `Ctrl + Alt + R` (tasks) |
127| Debug | `Ctrl + D` | `Alt + Shift + F9` |
128| Stop | `Cmd + F2` | `Ctrl + F2` |
129| Expand Macro | `Alt+Enter` | `Cmd + Shift + M` |
130
131### Unique to Zed
132
133| Action | Shortcut | Notes |
134| ----------------- | -------------------------- | ------------------------------ |
135| Toggle Right Dock | `Cmd + R` | Assistant panel, notifications |
136| Split Panes | `Cmd + K`, then arrow keys | Create splits in any direction |
137
138### How to Customize Keybindings
139
140- Open the Command Palette (`Cmd+Shift+A` or `Shift Shift`)
141- Run `Zed: Open Keymap Editor`
142
143This opens a list of all available bindings. You can override individual shortcuts or remove conflicts.
144
145Zed also supports key sequences (multi-key shortcuts).
146
147## Differences in User Interfaces
148
149### Different Analysis Engines
150
151RustRover uses its own proprietary code analysis engine for Rust intelligence. Zed uses rust-analyzer via the Language Server Protocol (LSP).
152
153What this means for you:
154
155- **Completions, go-to-definition, find usages, type inference** — All available in Zed via rust-analyzer
156- **Macro expansion** — Available in both (use `Cmd+Shift+M` in Zed)
157- **Inlay hints** — Both support type hints, parameter hints, and chaining hints
158
159Where you might notice differences:
160
161- Some refactorings available in RustRover may not have rust-analyzer equivalents
162- RustRover-specific inspections (beyond Clippy) won't exist in Zed
163- rust-analyzer is configured via JSON in Zed, not through a GUI
164
165**How to adapt:**
166
167- Use `Alt+Enter` for available code actions—rust-analyzer provides many
168- Configure rust-analyzer settings in `.zed/settings.json` for project-specific needs
169- Run `cargo clippy` for linting (it integrates with rust-analyzer diagnostics)
170
171### Project Configuration
172
173Both editors store per-project configuration in a hidden folder. RustRover uses `.idea` (with XML files), Zed uses `.zed` (with JSON files).
174
175**Run configurations don't transfer.** RustRover stores run/debug configurations in `.idea`. These have no automatic migration path. You'll recreate them as Zed [tasks](../tasks.md) in `.zed/tasks.json` and debug configurations in `.zed/debug.json`.
176
177**No Cargo tool window.** RustRover provides a visual tree of your workspace members, targets, features, and dependencies. Zed doesn't have this. You work with `Cargo.toml` and the Cargo CLI directly.
178
179**Toolchain management is external.** RustRover lets you select and switch toolchains in its settings UI. In Zed, you manage toolchains through `rustup`.
180
181**Configuration is opt-in.** RustRover auto-generates `.idea` when you open a project. Zed doesn't generate anything. You create `.zed/settings.json`, `tasks.json`, and `debug.json` as needed.
182
183**How to adapt:**
184
185- Create a `.zed/settings.json` in your project root for project-specific settings
186- Define common commands in `tasks.json` (open via Command Palette: `zed: open tasks`):
187
188```json
189[
190 {
191 "label": "cargo run",
192 "command": "cargo run"
193 },
194 {
195 "label": "cargo build",
196 "command": "cargo build"
197 },
198 {
199 "label": "cargo test",
200 "command": "cargo test"
201 },
202 {
203 "label": "cargo clippy",
204 "command": "cargo clippy"
205 },
206 {
207 "label": "cargo run --release",
208 "command": "cargo run --release"
209 }
210]
211```
212
213- Use `Ctrl+Alt+R` to run tasks quickly
214- Lean on your terminal (`Alt+F12`) for anything tasks don't cover
215
216### No Cargo Integration UI
217
218RustRover's Cargo tool window provides visual access to your project's targets, dependencies, and common Cargo commands. You can run builds, tests, and benchmarks with a click.
219
220Zed doesn't have a Cargo GUI. You work with Cargo through:
221
222- **Terminal** — Run any Cargo command directly
223- **Tasks** — Define shortcuts for common commands
224- **Gutter icons** — Run tests and binaries with clickable icons
225
226**How to adapt:**
227
228- Get comfortable with Cargo CLI commands: `cargo build`, `cargo run`, `cargo test`, `cargo clippy`, `cargo doc`
229- Use tasks for commands you run frequently
230- For dependency management, edit `Cargo.toml` directly (rust-analyzer provides completions for crate names and versions)
231
232### Tool Windows vs. Docks
233
234RustRover organizes auxiliary views into numbered tool windows (Project = 1, Cargo = Alt+1, Terminal = Alt+F12, etc.). Zed uses a similar concept called "docks":
235
236| RustRover Tool Window | Zed Equivalent | Shortcut (JetBrains keymap) |
237| --------------------- | -------------- | --------------------------- |
238| Project (1) | Project Panel | `Cmd + 1` |
239| Git (9 or Cmd+0) | Git Panel | `Cmd + 0` |
240| Terminal (Alt+F12) | Terminal Panel | `Alt + F12` |
241| Structure (7) | Outline Panel | `Cmd + 7` |
242| Problems (6) | Diagnostics | `Cmd + 6` |
243| Debug (5) | Debug Panel | `Cmd + 5` |
244
245Zed has three dock positions: left, bottom, and right. Panels can be moved between docks by dragging or through settings.
246
247Note that there's no dedicated Cargo tool window in Zed. Use the terminal or define tasks for your common Cargo commands.
248
249### Debugging
250
251Both RustRover and Zed offer integrated debugging for Rust, but using different backends:
252
253- RustRover uses its own debugger integration
254- Zed uses **CodeLLDB** (the same debug adapter popular in VS Code)
255
256To debug Rust code in Zed:
257
258- Set breakpoints with `Ctrl+F8`
259- Start debugging with `Alt+Shift+F9` or press `F4` and select a debug target
260- Step through code with `F7` (step into), `F8` (step over), `Shift+F8` (step out)
261- Continue execution with `F9`
262
263Zed can automatically detect debuggable targets in your Cargo project. Press `F4` to see available options.
264
265For more control, create a `.zed/debug.json` file:
266
267```json
268[
269 {
270 "label": "Debug Binary",
271 "adapter": "CodeLLDB",
272 "request": "launch",
273 "program": "${workspaceFolder}/target/debug/my_project"
274 },
275 {
276 "label": "Debug Tests",
277 "adapter": "CodeLLDB",
278 "request": "launch",
279 "cargo": {
280 "args": ["test", "--no-run"],
281 "filter": {
282 "kind": "test"
283 }
284 }
285 },
286 {
287 "label": "Debug with Arguments",
288 "adapter": "CodeLLDB",
289 "request": "launch",
290 "program": "${workspaceFolder}/target/debug/my_project",
291 "args": ["--config", "dev.toml"]
292 }
293]
294```
295
296### Running Tests
297
298RustRover has a dedicated test runner with a visual interface showing pass/fail status for each test. Zed provides test running through:
299
300- **Gutter icons** — Click the play button next to `#[test]` functions or test modules
301- **Tasks** — Define `cargo test` commands in `tasks.json`
302- **Terminal** — Run `cargo test` directly
303
304The test output appears in the terminal panel. For more detailed output, use:
305
306- `cargo test -- --nocapture` to see println! output
307- `cargo test -- --test-threads=1` for sequential test execution
308- `cargo test specific_test_name` to run a single test
309
310### Extensions vs. Plugins
311
312RustRover has a full JetBrains plugin catalog.
313
314Zed's extension catalog is smaller and more focused:
315
316- Language support and syntax highlighting
317- Themes
318- Slash commands for AI
319- Context servers
320
321Several features that might require plugins in other editors are built into Zed:
322
323- Real-time collaboration with voice chat
324- AI coding assistance
325- Built-in terminal
326- Task runner
327- rust-analyzer integration
328- rustfmt formatting
329
330### What's Not in Zed
331
332Here's what RustRover offers that Zed doesn't have:
333
334- **Profiler integration** — Use `cargo flamegraph`, `perf`, or external profiling tools
335- **Database tools** — Use DataGrip, DBeaver, or TablePlus
336- **HTTP Client** — Use tools like `curl`, `httpie`, or Postman
337- **Coverage visualization** — Use `cargo tarpaulin` or `cargo llvm-cov` externally
338
339## A Note on Licensing and Telemetry
340
341On licensing and telemetry:
342
343- **Zed is open source** (MIT licensed for the editor, AGPL for collaboration services)
344- **Telemetry is optional** and can be disabled during onboarding or in settings
345
346## Collaboration in Zed vs. RustRover
347
348RustRover offers Code With Me as a separate feature for collaboration. Zed has collaboration built into the core experience.
349
350- Open the Collab Panel in the left dock
351- Create a channel and [invite your collaborators](https://zed.dev/docs/collaboration#inviting-a-collaborator) to join
352- [Share your screen or your codebase](https://zed.dev/docs/collaboration#share-a-project) directly
353
354Once connected, you'll see each other's cursors, selections, and edits in real time. Voice chat is included. There's no need for separate tools or third-party logins.
355
356## Using AI in Zed
357
358Zed has built-in AI features. If you've used JetBrains AI Assistant, here's how to get set up.
359
360### Configuring GitHub Copilot
361
3621. Open Settings with `Cmd+,` (macOS) or `Ctrl+,` (Linux/Windows)
3632. Navigate to **AI → Edit Predictions**
3643. Click **Configure** next to "Configure Providers"
3654. Under **GitHub Copilot**, click **Sign in to GitHub**
366
367Once signed in, just start typing. Zed will offer suggestions inline for you to accept.
368
369### Additional AI Options
370
371To use other AI models in Zed, you have several options:
372
373- Use Zed's hosted models, with higher rate limits. Requires [authentication](https://zed.dev/docs/authentication) and subscription to [Zed Pro](https://zed.dev/docs/ai/subscription.html).
374- Bring your own [API keys](https://zed.dev/docs/ai/llm-providers.html), no authentication needed
375- Use [external agents like Claude Agent](https://zed.dev/docs/ai/external-agents.html)
376
377## Advanced Config and Productivity Tweaks
378
379Zed exposes advanced settings for power users who want to fine-tune their environment.
380
381Here are a few useful tweaks for Rust developers:
382
383**Format on Save (uses rustfmt by default):**
384
385```json
386"format_on_save": "on"
387```
388
389**Configure inlay hints for Rust:**
390
391```json
392{
393 "inlay_hints": {
394 "enabled": true,
395 "show_type_hints": true,
396 "show_parameter_hints": true,
397 "show_other_hints": true
398 }
399}
400```
401
402**Configure rust-analyzer settings** (requires manual JSON editing):
403
404```json
405{
406 "lsp": {
407 "rust-analyzer": {
408 "initialization_options": {
409 "checkOnSave": {
410 "command": "clippy"
411 },
412 "cargo": {
413 "allFeatures": true
414 },
415 "procMacro": {
416 "enable": true
417 }
418 }
419 }
420 }
421}
422```
423
424**Use a separate target directory for rust-analyzer (faster builds):**
425
426```json
427{
428 "lsp": {
429 "rust-analyzer": {
430 "initialization_options": {
431 "rust-analyzer.cargo.targetDir": true
432 }
433 }
434 }
435}
436```
437
438This tells rust-analyzer to use `target/rust-analyzer` instead of `target`, so IDE analysis doesn't conflict with your manual `cargo build` commands.
439
440**Enable direnv support (useful for Rust projects using direnv):**
441
442```json
443"load_direnv": "shell_hook"
444```
445
446**Configure linked projects for workspaces:**
447
448If you work with multiple Cargo projects that aren't in a workspace, you can tell rust-analyzer about them:
449
450```json
451{
452 "lsp": {
453 "rust-analyzer": {
454 "initialization_options": {
455 "linkedProjects": ["./project-a/Cargo.toml", "./project-b/Cargo.toml"]
456 }
457 }
458 }
459}
460```
461
462## Next Steps
463
464Now that you're set up, here are some resources to help you get the most out of Zed:
465
466- [All Settings](../reference/all-settings.md) — Customize settings, themes, and editor behavior
467- [Key Bindings](../key-bindings.md) — Learn how to customize and extend your keymap
468- [Tasks](../tasks.md) — Set up build and run commands for your projects
469- [AI Features](../ai/overview.md) — Explore Zed's AI capabilities beyond code completion
470- [Collaboration](../collaboration/overview.md) — Share your projects and code together in real time
471- [Rust in Zed](../languages/rust.md) — Rust-specific setup and configuration