How to Migrate from RustRover to Zed

This guide covers keybindings, settings, and the differences you'll encounter as a Rust developer switching from RustRover.

Install Zed

Zed is available on macOS, Windows, and Linux.

For macOS, you can download it from zed.dev/download, or install via Homebrew:

brew install --cask zed

For Windows, download the installer from zed.dev/download, or install via winget:

winget install Zed.Zed

For most Linux users, the easiest way to install Zed is through our installation script:

curl -f https://zed.dev/install.sh | sh

After installation, you can launch Zed from your Applications folder (macOS), Start menu (Windows), or directly from the terminal using: zed . This opens the current directory in Zed.

Set Up the JetBrains Keymap

If 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:

1. Open Settings with Cmd+, (macOS) or Ctrl+, (Linux/Windows)
2. Search for Base Keymap
3. Select JetBrains

This maps familiar shortcuts like Shift Shift for Search Everywhere, Cmd+O for Go to Class, and Cmd+Shift+A for Find Action.

Set Up Editor Preferences

You 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.

Settings RustRover users typically configure first:

Zed also supports per-project settings. Create a .zed/settings.json file in your project root to override global settings for that project.

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.

Open or Create a Project

After setup, press Cmd+Shift+O (with JetBrains keymap) to open a folder. This becomes your workspace in Zed.

To start a new project, use Cargo from the terminal:

cargo new my_project
cd my_project
zed .

Or for a library:

cargo new --lib my_library

You can also launch Zed from the terminal inside any existing Cargo project with: zed .

Once inside a project:

• Use Cmd+Shift+O or Cmd+E to jump between files quickly (like RustRover's "Recent Files")
• Use Cmd+Shift+A or Shift Shift to open the Command Palette (like RustRover's "Search Everywhere")
• Use Cmd+O to search for symbols (like RustRover's "Go to Symbol")

Open 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).

Differences in Keybindings

If 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.

Common Shared Keybindings

Different Keybindings (RustRover → Zed)

Unique to Zed

How to Customize Keybindings

• Open the Command Palette (Cmd+Shift+A or Shift Shift)
• Run Zed: Open Keymap Editor

This opens a list of all available bindings. You can override individual shortcuts or remove conflicts.

Zed also supports key sequences (multi-key shortcuts).

Differences in User Interfaces

Different Analysis Engines

RustRover uses its own proprietary code analysis engine for Rust intelligence. Zed uses rust-analyzer via the Language Server Protocol (LSP).

What this means for you:

• Completions, go-to-definition, find usages, type inference — All available in Zed via rust-analyzer
• Macro expansion — Available in both (use Cmd+Shift+M in Zed)
• Inlay hints — Both support type hints, parameter hints, and chaining hints

Where you might notice differences:

• Some refactorings available in RustRover may not have rust-analyzer equivalents
• RustRover-specific inspections (beyond Clippy) won't exist in Zed
• rust-analyzer is configured via JSON in Zed, not through a GUI

How to adapt:

• Use Alt+Enter for available code actions—rust-analyzer provides many
• Configure rust-analyzer settings in .zed/settings.json for project-specific needs
• Run cargo clippy for linting (it integrates with rust-analyzer diagnostics)

Project Configuration

Both editors store per-project configuration in a hidden folder. RustRover uses .idea (with XML files), Zed uses .zed (with JSON files).

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 in .zed/tasks.json and debug configurations in .zed/debug.json.

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.

Toolchain management is external. RustRover lets you select and switch toolchains in its settings UI. In Zed, you manage toolchains through rustup.

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.

How to adapt:

• Create a .zed/settings.json in your project root for project-specific settings
• Define common commands in tasks.json (open via Command Palette: zed: open tasks):

[
  {
    "label": "cargo run",
    "command": "cargo run"
  },
  {
    "label": "cargo build",
    "command": "cargo build"
  },
  {
    "label": "cargo test",
    "command": "cargo test"
  },
  {
    "label": "cargo clippy",
    "command": "cargo clippy"
  },
  {
    "label": "cargo run --release",
    "command": "cargo run --release"
  }
]

• Use Ctrl+Alt+R to run tasks quickly
• Lean on your terminal (Alt+F12) for anything tasks don't cover

No Cargo Integration UI

RustRover'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.

Zed doesn't have a Cargo GUI. You work with Cargo through:

• Terminal — Run any Cargo command directly
• Tasks — Define shortcuts for common commands
• Gutter icons — Run tests and binaries with clickable icons

How to adapt:

• Get comfortable with Cargo CLI commands: cargo build, cargo run, cargo test, cargo clippy, cargo doc
• Use tasks for commands you run frequently
• For dependency management, edit Cargo.toml directly (rust-analyzer provides completions for crate names and versions)

Tool Windows vs. Docks

RustRover organizes auxiliary views into numbered tool windows (Project = 1, Cargo = Alt+1, Terminal = Alt+F12, etc.). Zed uses a similar concept called "docks":

Zed has three dock positions: left, bottom, and right. Panels can be moved between docks by dragging or through settings.

Note that there's no dedicated Cargo tool window in Zed. Use the terminal or define tasks for your common Cargo commands.

Debugging

Both RustRover and Zed offer integrated debugging for Rust, but using different backends:

• RustRover uses its own debugger integration
• Zed uses CodeLLDB (the same debug adapter popular in VS Code)

To debug Rust code in Zed:

• Set breakpoints with Ctrl+F8
• Start debugging with Alt+Shift+F9 or press F4 and select a debug target
• Step through code with F7 (step into), F8 (step over), Shift+F8 (step out)
• Continue execution with F9

Zed can automatically detect debuggable targets in your Cargo project. Press F4 to see available options.

For more control, create a .zed/debug.json file:

[
  {
    "label": "Debug Binary",
    "adapter": "CodeLLDB",
    "request": "launch",
    "program": "${workspaceFolder}/target/debug/my_project"
  },
  {
    "label": "Debug Tests",
    "adapter": "CodeLLDB",
    "request": "launch",
    "cargo": {
      "args": ["test", "--no-run"],
      "filter": {
        "kind": "test"
      }
    }
  },
  {
    "label": "Debug with Arguments",
    "adapter": "CodeLLDB",
    "request": "launch",
    "program": "${workspaceFolder}/target/debug/my_project",
    "args": ["--config", "dev.toml"]
  }
]

Running Tests

RustRover has a dedicated test runner with a visual interface showing pass/fail status for each test. Zed provides test running through:

• Gutter icons — Click the play button next to #[test] functions or test modules
• Tasks — Define cargo test commands in tasks.json
• Terminal — Run cargo test directly

The test output appears in the terminal panel. For more detailed output, use:

• cargo test -- --nocapture to see println! output
• cargo test -- --test-threads=1 for sequential test execution
• cargo test specific_test_name to run a single test

Extensions vs. Plugins

RustRover has a full JetBrains plugin catalog.

Zed's extension catalog is smaller and more focused:

• Language support and syntax highlighting
• Themes
• Slash commands for AI
• Context servers

Several features that might require plugins in other editors are built into Zed:

• Real-time collaboration with voice chat
• AI coding assistance
• Built-in terminal
• Task runner
• rust-analyzer integration
• rustfmt formatting

What's Not in Zed

Here's what RustRover offers that Zed doesn't have:

• Profiler integration — Use cargo flamegraph, perf, or external profiling tools
• Database tools — Use DataGrip, DBeaver, or TablePlus
• HTTP Client — Use tools like curl, httpie, or Postman
• Coverage visualization — Use cargo tarpaulin or cargo llvm-cov externally

A Note on Licensing and Telemetry

On licensing and telemetry:

• Zed is open source (MIT licensed for the editor, AGPL for collaboration services)
• Telemetry is optional and can be disabled during onboarding or in settings

Collaboration in Zed vs. RustRover

RustRover offers Code With Me as a separate feature for collaboration. Zed has collaboration built into the core experience.

• Open the Collab Panel in the left dock
• Create a channel and invite your collaborators to join
• Share your screen or your codebase directly

Once 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.

Using AI in Zed

Zed has built-in AI features. If you've used JetBrains AI Assistant, here's how to get set up.

Configuring GitHub Copilot

1. Open Settings with Cmd+, (macOS) or Ctrl+, (Linux/Windows)
2. Navigate to AI → Edit Predictions
3. Click Configure next to "Configure Providers"
4. Under GitHub Copilot, click Sign in to GitHub

Once signed in, just start typing. Zed will offer suggestions inline for you to accept.

Additional AI Options

To use other AI models in Zed, you have several options:

• Use Zed's hosted models, with higher rate limits. Requires authentication and subscription to Zed Pro.
• Bring your own API keys, no authentication needed
• Use external agents like Claude Agent

Advanced Config and Productivity Tweaks

Zed exposes advanced settings for power users who want to fine-tune their environment.

Here are a few useful tweaks for Rust developers:

Format on Save (uses rustfmt by default):

"format_on_save": "on"

Configure inlay hints for Rust:

{
  "inlay_hints": {
    "enabled": true,
    "show_type_hints": true,
    "show_parameter_hints": true,
    "show_other_hints": true
  }
}

Configure rust-analyzer settings (requires manual JSON editing):

{
  "lsp": {
    "rust-analyzer": {
      "initialization_options": {
        "checkOnSave": {
          "command": "clippy"
        },
        "cargo": {
          "allFeatures": true
        },
        "procMacro": {
          "enable": true
        }
      }
    }
  }
}

Use a separate target directory for rust-analyzer (faster builds):

{
  "lsp": {
    "rust-analyzer": {
      "initialization_options": {
        "rust-analyzer.cargo.targetDir": true
      }
    }
  }
}

This tells rust-analyzer to use target/rust-analyzer instead of target, so IDE analysis doesn't conflict with your manual cargo build commands.

Enable direnv support (useful for Rust projects using direnv):

"load_direnv": "shell_hook"

Configure linked projects for workspaces:

If you work with multiple Cargo projects that aren't in a workspace, you can tell rust-analyzer about them:

{
  "lsp": {
    "rust-analyzer": {
      "initialization_options": {
        "linkedProjects": ["./project-a/Cargo.toml", "./project-b/Cargo.toml"]
      }
    }
  }
}

Next Steps

Now that you're set up, here are some resources to help you get the most out of Zed:

• All Settings — Customize settings, themes, and editor behavior
• Key Bindings — Learn how to customize and extend your keymap
• Tasks — Set up build and run commands for your projects
• AI Features — Explore Zed's AI capabilities beyond code completion
• Collaboration — Share your projects and code together in real time
• Rust in Zed — Rust-specific setup and configuration