1---
2title: How to Migrate from PyCharm to Zed
3description: "Guide for migrating from PyCharm to Zed, including settings and keybindings."
4---
5
6# How to Migrate from PyCharm to Zed
7
8This guide covers how to set up Zed if you're coming from PyCharm, including keybindings, settings, and the differences you should expect.
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 PyCharm, 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 PyCharm 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. |
55| `soft_wrap` | Wrap long lines. Options: `"none"`, `"editor_width"`, `"preferred_line_length"` |
56| `preferred_line_length` | Column width for wrapping and rulers. Default is 80, PEP 8 recommends 79. |
57| `inlay_hints` | Show parameter names and type hints inline, like PyCharm's hints. |
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, similar to how you might use `.idea` folders in PyCharm.
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. Unlike PyCharm, there's no project configuration wizard, no interpreter selection dialog, and no project structure setup required.
67
68To start a new project, create a directory using your terminal or file manager, then open it in Zed. The editor will treat that folder as the root of your project.
69
70You can also launch Zed from the terminal inside any folder with:
71`zed .`
72
73Once inside a project:
74
75- Use `Cmd+Shift+O` or `Cmd+E` to jump between files quickly (like PyCharm's "Recent Files")
76- Use `Cmd+Shift+A` or `Shift Shift` to open the Command Palette (like PyCharm's "Search Everywhere")
77- Use `Cmd+O` to search for symbols (like PyCharm's "Go to Symbol")
78
79Open buffers appear as tabs across the top. The Project Panel shows your file tree and Git status. Toggle it with `Cmd+1` (just like PyCharm's Project tool window).
80
81## Differences in Keybindings
82
83If 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 PyCharm.
84
85### Common Shared Keybindings
86
87| Action | Shortcut |
88| ----------------------------- | ----------------------- |
89| Search Everywhere | `Shift Shift` |
90| Find Action / Command Palette | `Cmd + Shift + A` |
91| Go to File | `Cmd + Shift + O` |
92| Go to Symbol | `Cmd + O` |
93| Recent Files | `Cmd + E` |
94| Go to Definition | `Cmd + B` |
95| Find Usages | `Alt + F7` |
96| Rename Symbol | `Shift + F6` |
97| Reformat Code | `Cmd + Alt + L` |
98| Toggle Project Panel | `Cmd + 1` |
99| Toggle Terminal | `Alt + F12` |
100| Duplicate Line | `Cmd + D` |
101| Delete Line | `Cmd + Backspace` |
102| Move Line Up/Down | `Shift + Alt + Up/Down` |
103| Expand/Shrink Selection | `Alt + Up/Down` |
104| Comment Line | `Cmd + /` |
105| Go Back / Forward | `Cmd + [` / `Cmd + ]` |
106| Toggle Breakpoint | `Ctrl + F8` |
107
108### Different Keybindings (PyCharm → Zed)
109
110| Action | PyCharm | Zed (JetBrains keymap) |
111| ---------------------- | ----------- | ------------------------ |
112| File Structure | `Cmd + F12` | `Cmd + F12` (outline) |
113| Navigate to Next Error | `F2` | `F2` |
114| Run | `Ctrl + R` | `Ctrl + Alt + R` (tasks) |
115| Debug | `Ctrl + D` | `Alt + Shift + F9` |
116| Stop | `Cmd + F2` | `Ctrl + F2` |
117
118### Unique to Zed
119
120| Action | Shortcut | Notes |
121| ----------------- | -------------------------- | ------------------------------ |
122| Toggle Right Dock | `Cmd + R` | Assistant panel, notifications |
123| Split Panes | `Cmd + K`, then arrow keys | Create splits in any direction |
124
125### How to Customize Keybindings
126
127- Open the Command Palette (`Cmd+Shift+A` or `Shift Shift`)
128- Run `Zed: Open Keymap Editor`
129
130This opens a list of all available bindings. You can override individual shortcuts or remove conflicts.
131
132Zed also supports key sequences (multi-key shortcuts).
133
134## Differences in User Interfaces
135
136### No Indexing
137
138If you've used PyCharm on large projects, you know the wait: "Indexing..." can take anywhere from 30 seconds to several minutes depending on project size and dependencies. PyCharm builds a comprehensive index of your entire codebase to power its code intelligence, and it re-indexes when dependencies change or when you install new packages.
139
140Zed doesn't index. You open a folder and start working immediately. File search and navigation stay fast regardless of project size, without waiting through indexing pauses.
141
142PyCharm's index powers features like finding all usages across your entire codebase, understanding class hierarchies, and detecting unused imports project-wide. Zed delegates this work to language servers, which may not analyze as deeply or as broadly.
143
144**How to adapt:**
145
146- For project-wide symbol search, use `Cmd+O` / Go to Symbol (relies on your language server)
147- For finding files by name, use `Cmd+Shift+O` / Go to File
148- For text search across files, use `Cmd+Shift+F`—this is fast even on large codebases
149- For deep static analysis, consider running tools like `mypy`, `pylint`, or `ruff check` from the terminal
150
151### LSP vs. Native Language Intelligence
152
153PyCharm has its own language analysis engine built specifically for Python. This engine understands your code deeply: it resolves types without annotations, tracks data flow, knows about Django models and Flask routes, and offers specialized refactorings.
154
155Zed uses the Language Server Protocol (LSP) for code intelligence. For Python, Zed provides several language servers out of the box:
156
157- **basedpyright** (default) — Fast type checking and completions
158- **Ruff** (default) — Linting and formatting
159- **ty** — Up-and-coming language server from Astral, built for speed
160- **Pyright** — Microsoft's type checker
161- **PyLSP** — Plugin-based server with tool integrations
162
163The LSP experience for Python is strong. basedpyright provides accurate completions, type checking, and navigation. Ruff handles formatting and linting with excellent performance.
164
165Where you might notice differences:
166
167- Framework-specific intelligence (Django ORM, Flask routes) isn't built-in
168- Some complex refactorings (extract method with proper scope analysis) may be less sophisticated
169- Auto-import suggestions depend on what the language server knows about your environment
170
171**How to adapt:**
172
173- Use `Alt+Enter` for available code actions—the list will vary by language server
174- Ensure your virtual environment is selected so the language server can resolve your dependencies
175- Use Ruff for fast, consistent formatting (it's enabled by default)
176- For code inspection similar to PyCharm's "Inspect Code," run `ruff check .` or check the Diagnostics panel (`Cmd+6`)—basedpyright and Ruff together catch many of the same issues
177
178### Virtual Environments and Interpreters
179
180In PyCharm, you select a Python interpreter through a GUI, and PyCharm manages the connection between your project and that interpreter. It shows available packages, lets you install new ones, and keeps track of which environment each project uses.
181
182Zed handles virtual environments through its toolchain system:
183
184- Zed automatically discovers virtual environments in common locations (`.venv`, `venv`, `.env`, `env`)
185- When a virtual environment is detected, the terminal auto-activates it
186- Language servers are automatically configured to use the discovered environment
187- You can manually select a toolchain if auto-detection picks the wrong one
188
189**How to adapt:**
190
191- Create your virtual environment with `python -m venv .venv` or `uv sync`
192- Open the folder in Zed—it will detect the environment automatically
193- If you need to switch environments, use the toolchain selector
194- For conda environments, ensure they're activated in your shell before launching Zed
195
196> **Tip:** If basedpyright shows import errors for packages you've installed, check that Zed has selected the correct virtual environment. Use the toolchain selector to verify or change the active environment.
197
198### No Project Model
199
200PyCharm manages projects through `.idea` folders containing XML configuration files, interpreter assignments, and run configurations. This model lets PyCharm remember your interpreter choice, manage dependencies through the UI, and persist complex run/debug setups.
201
202Zed has no project model. A project is a folder. There's no wizard, no interpreter selection screen, no project structure configuration.
203
204This means:
205
206- Run configurations don't exist. You define tasks or use the terminal. Your existing PyCharm run configs in `.idea/` won't be read—you'll recreate the ones you need in `tasks.json`.
207- Interpreter management is external. Zed discovers environments but doesn't create them.
208- Dependencies are managed through pip, uv, poetry, or conda—not through the editor.
209- There's no Python Console (interactive REPL) panel. Use `python` or `ipython` in the terminal instead.
210
211**How to adapt:**
212
213- Create a `.zed/settings.json` in your project root for project-specific settings
214- Define common commands in `tasks.json` (open via Command Palette: `zed: open tasks`):
215
216```json
217[
218 {
219 "label": "run",
220 "command": "python main.py"
221 },
222 {
223 "label": "test",
224 "command": "pytest"
225 },
226 {
227 "label": "test current file",
228 "command": "pytest $ZED_FILE"
229 }
230]
231```
232
233- Use `Ctrl+Alt+R` to run tasks quickly
234- Lean on your terminal (`Alt+F12`) for anything tasks don't cover
235
236### No Framework Integration
237
238PyCharm Professional's value for web development comes largely from its framework integration. Django templates are understood and navigable. Flask routes are indexed. SQLAlchemy models get special treatment. Template variables autocomplete.
239
240Zed has none of this. The language server sees Python code as Python code—it doesn't understand that `@app.route` defines an endpoint or that a Django model class creates database tables.
241
242**How to adapt:**
243
244- Use grep and file search liberally. `Cmd+Shift+F` with a regex can find route definitions, model classes, or template usages.
245- Rely on your language server's "find references" (`Alt+F7`) for navigation—it works, just without framework context
246- Consider using framework-specific CLI tools (`python manage.py`, `flask routes`) from Zed's terminal
247
248> **Tip:** For database work, pick up a dedicated tool like DataGrip, DBeaver, or TablePlus. Many developers who switch to Zed keep DataGrip around specifically for SQL.
249
250### Tool Windows vs. Docks
251
252PyCharm organizes auxiliary views into numbered tool windows (Project = 1, Python Console = 4, Terminal = Alt+F12, etc.). Zed uses a similar concept called "docks":
253
254| PyCharm Tool Window | Zed Equivalent | Shortcut (JetBrains keymap) |
255| ------------------- | -------------- | --------------------------- |
256| Project (1) | Project Panel | `Cmd + 1` |
257| Git (9 or Cmd+0) | Git Panel | `Cmd + 0` |
258| Terminal (Alt+F12) | Terminal Panel | `Alt + F12` |
259| Structure (7) | Outline Panel | `Cmd + 7` |
260| Problems (6) | Diagnostics | `Cmd + 6` |
261| Debug (5) | Debug Panel | `Cmd + 5` |
262
263Zed has three dock positions: left, bottom, and right. Panels can be moved between docks by dragging or through settings.
264
265### Debugging
266
267Both PyCharm and Zed offer integrated debugging, but the experience differs:
268
269- Zed uses `debugpy` (the same debug adapter that VS Code uses)
270- Set breakpoints with `Ctrl+F8`
271- Start debugging with `Alt+Shift+F9` or press `F4` and select a debug target
272- Step through code with `F7` (step into), `F8` (step over), `Shift+F8` (step out)
273- Continue execution with `F9`
274
275Zed can automatically detect debuggable entry points. Press `F4` to see available options, including:
276
277- Python scripts
278- Modules
279- pytest tests
280
281For more control, create a `.zed/debug.json` file:
282
283```json
284[
285 {
286 "label": "Debug Current File",
287 "adapter": "Debugpy",
288 "program": "$ZED_FILE",
289 "request": "launch"
290 },
291 {
292 "label": "Debug Flask App",
293 "adapter": "Debugpy",
294 "request": "launch",
295 "module": "flask",
296 "args": ["run", "--debug"],
297 "env": {
298 "FLASK_APP": "app.py"
299 }
300 }
301]
302```
303
304### Running Tests
305
306PyCharm has a dedicated test runner with a visual interface showing pass/fail status for each test. Zed provides test running through:
307
308- **Gutter icons** — Click the play button next to test functions or classes
309- **Tasks** — Define pytest or unittest commands in `tasks.json`
310- **Terminal** — Run `pytest` directly
311
312The test output appears in the terminal panel. For pytest, use `--tb=short` for concise tracebacks or `-v` for verbose output.
313
314### Extensions vs. Plugins
315
316PyCharm has a large plugin catalog covering everything from additional language support to database tools to deployment integrations.
317
318Zed's extension catalog is smaller and more focused:
319
320- Language support and syntax highlighting
321- Themes
322- Slash commands for AI
323- Context servers
324
325Several features that require plugins in PyCharm are built into Zed:
326
327- Real-time collaboration with voice chat
328- AI coding assistance
329- Built-in terminal
330- Task runner
331- LSP-based code intelligence
332- Ruff formatting and linting
333
334### What's Not in Zed
335
336To set expectations clearly, here's what PyCharm offers that Zed doesn't have:
337
338- **Scientific Mode / Jupyter integration** — For notebooks and data science workflows, use JupyterLab or VS Code with the Jupyter extension alongside Zed for your Python editing
339- **Database tools** — Use DataGrip, DBeaver, or TablePlus
340- **Django/Flask template navigation** — Use file search and grep
341- **Visual package manager** — Use pip, uv, or poetry from the terminal
342- **Remote interpreters** — Zed has remote development, but it works differently
343- **Profiler integration** — Use cProfile, py-spy, or similar tools externally
344
345## Collaboration in Zed vs. PyCharm
346
347PyCharm offers Code With Me as a separate plugin for collaboration. Zed has collaboration built into the core experience.
348
349- Open the Collab Panel in the left dock
350- Create a channel and [invite your collaborators](https://zed.dev/docs/collaboration#inviting-a-collaborator) to join
351- [Share your screen or your codebase](https://zed.dev/docs/collaboration#share-a-project) directly
352
353Once 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.
354
355## Using AI in Zed
356
357If you're used to AI assistants in PyCharm (like GitHub Copilot or JetBrains AI Assistant), Zed offers similar capabilities with more flexibility.
358
359### Configuring GitHub Copilot
360
3611. Open Settings with `Cmd+,` (macOS) or `Ctrl+,` (Linux/Windows)
3622. Navigate to **AI → Edit Predictions**
3633. Click **Configure** next to "Configure Providers"
3644. Under **GitHub Copilot**, click **Sign in to GitHub**
365
366Once signed in, just start typing. Zed will offer suggestions inline for you to accept.
367
368### Additional AI Options
369
370To use other AI models in Zed, you have several options:
371
372- 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).
373- Bring your own [API keys](https://zed.dev/docs/ai/llm-providers.html), no authentication needed
374- Use [external agents like Claude Agent](https://zed.dev/docs/ai/external-agents.html)
375
376## Advanced Config and Productivity Tweaks
377
378Zed exposes advanced settings for power users who want to fine-tune their environment.
379
380Here are a few useful tweaks:
381
382**Format on Save:**
383
384```json
385"format_on_save": "on"
386```
387
388**Enable direnv support (useful for Python projects using direnv):**
389
390```json
391"load_direnv": "shell_hook"
392```
393
394**Customize virtual environment detection** (requires manual JSON editing):
395
396```json
397{
398 "terminal": {
399 "detect_venv": {
400 "on": {
401 "directories": [".venv", "venv", ".env", "env"],
402 "activate_script": "default"
403 }
404 }
405 }
406}
407```
408
409**Configure basedpyright type checking strictness:**
410
411If you find basedpyright too strict or too lenient, configure it in your project's `pyrightconfig.json`:
412
413```json
414{
415 "typeCheckingMode": "basic"
416}
417```
418
419Options are `"off"`, `"basic"`, `"standard"` (default), `"strict"`, or `"all"`.
420
421## Next Steps
422
423Now that you're set up, here are some resources to help you get the most out of Zed:
424
425- [All Settings](../reference/all-settings.md) — Customize settings, themes, and editor behavior
426- [Key Bindings](../key-bindings.md) — Learn how to customize and extend your keymap
427- [Tasks](../tasks.md) — Set up build and run commands for your projects
428- [AI Features](../ai/overview.md) — Explore Zed's AI capabilities beyond code completion
429- [Collaboration](../collaboration/overview.md) — Share your projects and code together in real time
430- [Python in Zed](../languages/python.md) — Python-specific setup and configuration