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