In the landscape of code editors, few proposals raise as much conversation as Zed, driven by the team that brought Atom and Tree-sitter to life. With its open source code and focus on collaboration, performance, and extensibility, it has become an option that many developers look at with a magnifying glass for its promise of extreme speed and cooperative editing.
At first impressions, its startup stands out: on modern hardware such as an iMac with an M1 processor, practically instantaneous startups have been reported, on the order of hundredths of a second, and the project itself boasts startup figures below 60 milliseconds. Compared to popular Electron-based alternatives, users point out a much lighter feel even with extensions active, something that invites you to try if you value performance, fluidity and response times.
What is Zed Editor and who is behind it?
Zed is a Free and open source text and source code editor for macOS and Linux, with a Windows version in development and closed testing. The project was born after the Atom closure in 2022, when several major contributors kicked off the initiative and presented it in 2023. In 2024 the project was released as open source and, already in 2025, a significant funding round of $32 million led by Sequoia Capital was announced, reinforcing its traction, roadmap and continuity.
The repository is written primarily in Rust, which aligns well with its goals of performance and security. Licenses include AGPL, GPL, and Apache. The interface language is English, and the official website is zed.dev. The community has discussed its popularity on GitHub, with tens of thousands of likes demonstrating interest in an editor focused on both native experience as in collaboration.
Architecture, performance, and key technologies in Zed
Zed's promise is built on modern technologies: GPU rendering, native integration with Tree-sitter for incremental parsing, LSP support for editor intelligence, and DAP compatibility for debugging. This technical foundation enables it to offer efficient jumps, autocompletion, highlighting, refactoring, and debugging, along with multi-buffer editing and project management that impacts the minimal latency and a feeling of lightness.
Beyond the engine, a clean and tidy design stands out. The editor includes an integrated terminal, offers a CLI for integrating into command-line workflows, and includes diagnostics to detect problems in real time. It also includes keymaps that emulate shortcuts from popular IDEs, so the adaptation curve is shorter. All of this is accompanied by a very broad ecosystem of visual themes for those who want to fine-tune every last detail of the editor. aesthetics and usability.
Real-time collaboration and channels
One of Zed's biggest selling points is its focus on collaborative editing. The app lets you share the editor and screen, open channels, maintain text chats, and even audio chat with your team while working on the same file or project. This real-time co-editing capability also extends to interaction with AI agents, opening the door to human-computer pairing sessions. Some of these features require logging in with a GitHub account, and shared sessions have restrictions: for example, only the host can create or delete files, setting a clear standard for control over sharing. project structure and permissions.
Integrations, extensions, and autocomplete
The editor offers out-of-the-box support for most common languages, and expands from there via extensions. There's autocompletion for a multitude of frameworks and stacks via LSPs, and the catalog includes popular pieces like Emmet and dedicated support for ecosystems like Vue. For those who rely on code assistance, there's direct integration with GitHub Copilot and an architecture that supports additional LSP, DAP, and MCP servers via extensions, making it a flexible platform with a constantly expanding ecosystem.
Zed's built-in AI and freemium model
Zed's relationship with AI is twofold: on the one hand, it incorporates its own assistant capable of working with providers such as OpenAI and Claude, in addition to integrating with local models through Ollama; on the other hand, its real-time collaboration includes AI agents within the channels. It is worth keeping in mind that, starting in 2025, the project adopted a freemium model: the free version limits the number of predictive edits and generative queries per month, so certain intensive uses will require a subscription. Even with this nuance, the possibility of combining the native assistant with services such as Copilot and current large models, including those from the GPT 4o family, provides a layer of productivity in repetitive and exploration tasks.
Windows Platforms, Installation, and Status
On macOS and Linux you can download Zed directly or install it via the corresponding package manager — is also on FlathubOther platforms are not yet officially supported; Windows is currently in a closed testing phase, and there are unofficial paths that require you to compile the project yourself. This situation leaves macOS and Linux as priority environments for a stable experience. The team maintains documentation to contribute, with development guides and an open approach to incorporating improvements, in addition to job offers associated with product growth.
User experience: from the feeling of lightness to real life
Users who came from Electron-based editors comment that, after years of projects with C, Rust, Python, or Flutter extensions, the switch to Zed feels like a breath of fresh air: fast startup, lower power consumption, and an immediate interface response, even with a comparable set of extensions. This difference is especially noticeable when jumping between buffers, launching the integrated terminal, or invoking LSP actions. In a day-to-day life with many open files and frequent browsing of the project tree, the general feeling is that Zed remains agile, orderly and with little friction.
Configuration and customization via JSON
Zed configuration is done primarily in a JSON file. This has both advantages and disadvantages. The advantage: you can version your settings, sync them, and replicate your environment with surgical precision. The disadvantage: if you don't import the default template, you'll have to consult the documentation to remember every key. Common tweaks include docking panels (notifications, chat, main project panel, and outline view), disabling telemetry, using monospaced fonts like JetBrains Mono, and enabling Vim mode, with the option to match the shortcuts of popular editors.
Shortcuts, Vim mode, and relative numbering
If you work with Vim gestures, Zed lets you activate them globally and adjust shortcuts to match what you've used in other environments. It's common to combine it with relative line numbering to quickly jump through code. This set of habits, combined with the editor's low latency, makes editing particularly fluid. You can also select preconfigured keymaps that emulate familiar IDE experiences, reducing the adaptation time when using Zed. migrate from your previous tool.
Themes, extensions, and synchronization in Zed
The editor supports a long list of themes, including packages that replicate palettes from other IDEs. For example, if you like the look of Xcode, you can install an equivalent theme and apply it from the settings. Zed also allows you to declare a set of extensions to automatically install when you log in with the same sync account, very useful if you work with stacks like Flutter, Rust, or Python and want your environment to rebuild itself. This approach fits perfectly with the idea of ​​having a reproducible configuration and makes it easier to maintain a consistent experience across teams and machines.
Python environments and integrated terminal
For those who script frequently in Python, the automatic activation of virtual environments when opening the project terminal is a practical setting that prevents dependency errors. Although Zed does not include a graphical wizard to create virtual environments like other tools do, it can be configured to detect and activate the workspace environment as soon as a terminal is opened. This detail, combined with the presence of an integrated terminal, means that many automation and testing tasks remain within the editor, maintaining the workflow without context switches.
Copilot and large integrated models
If you already use Copilot in other editors, in Zed you can connect and combine it with the editor's own assistant. It also allows you to work with local models via Ollama and with well-known LLM providers. Some people prefer to align these capabilities with GPT 4o when the case calls for it, whether for code completion, transformations, or quick test generation. Everything is adjusted from the settings JSON file, without the need to navigate through multiple menus, which appeals to those who see the editor as a well-controlled declarative configuration file.
Licenses, compliance and CI with cargo-about
The repository uses cargo-about to manage third-party license compliance in the dependency chain. If continuous integration fails due to licensing issues, the project documents three main checks.
First, if a message appears indicating that no license is specified in your crate, it is a good idea to mark it with publish = false in the package section of Cargo.toml to prevent it from being published. Second, if a dependency does not meet the license requirements, its license must be identified and confirmed that the project's compliance system can cover it; if acceptable, its SPDX identifier is added to the accepted array of the script/licenses/zed-licenses.toml file. And third, if cargo-about cannot locate the license for a dependency, a clarification block must be added at the end of the same file, following the instructions in the cargo-about book. With these guidelines, the team keeps its pipeline green and respects the legal obligations of free software.
Debugging, Git, and remote work
Zed includes Git integration, so you can commit, review changes, and navigate the history from the editor itself. For debugging, DAP support opens the door to debugging multiple languages ​​with compatible adapters. It also supports remote development scenarios, reinforcing the collaborative approach that is the project's hallmark. Between this triad of Git, DAP, and remote, the editor covers a wide range of needs without burdening you with unnecessary extras, maintaining the lightweight, performance-oriented base.
Clear advantages and areas for improvement in Zed
There's a list of elements that many users highlight as positive: practically instant launch, clean design, active development, extensions for autocompletion in countless stacks, integration with Copilot, very fast collaboration with text and audio chat, editor and screen sharing, channels, support for serial languages, integrated terminal, a wide ecosystem of extensions such as Emmet or specific framework support, themes to bore, familiar keymaps, diagnostics, Vim mode and a CLI to orchestrate use from the console. All of this, in addition, is framed within a philosophy of not adding bloat and prioritizing a minimal but extensible experience.
On the improvement side, there are practical points: for now, macOS and Linux are the official platforms; Windows requires compiling or waiting for the closed beta to progress. The JSON configuration is extremely powerful but requires consulting documentation if you don't start from the default file, and a code style section as in-depth as that of JetBrains IDEs is missed, for example for aligning elements. Project management is limited to one instance per project and doesn't offer a compendium of recent projects as a launcher.
The AI ​​assistant is limited to OpenAI, Claude, and local models with Ollama. In collaboration, only the host can add or delete files. Some features require a GitHub account. There's no browser or embedded preview, and the Discord community lacks text channels, which limits its usefulness today. Still, the overall package maintains a very favorable balance for those looking for a collaborative project. speed, collaboration and fine control.
Who should try Zed and why
If you use web-based editors and find the experience slows down with large projects or projects with many extensions, Zed is a good candidate. It's also a good candidate if you value real-time co-editing or enjoy controlling your configuration through a declarative file, with synchronization and auto-installable extensions. For teams that want pair programming without relying on external tools, its system of channels, chats, and sharing reduces friction. And for those who already live with Vim motions, dedicated mode and relative numbering help maintain consistency. browsing and editing speed.
Ecosystem status and documentation
The project encourages contributions and has guides for doing so, with a CI that monitors licensing and quality. Beyond the repository and the official website, there are blog posts with practical configurations that describe how to dock panels, disable telemetry, set fonts and shortcuts, install Flutter, Rust and Python extensions, apply Xcode-like themes, automatically activate virtual environments in the terminal and connect AI providers. There is content on social platforms, although it is sometimes limited by browser requirements, which leaves the official site, GitHub and the documentation as the best source for learn and resolve everyday doubts.
After several weeks of use, those who have migrated point out that Zed is especially convenient for opening single files or medium-sized projects without having to load a heavy IDE; some continue to prefer suites like JetBrains for complex projects where a very specific set of tools is needed. But Zed's place in the toolbox is growing: fast for review, powerful for collaboration, and extensible enough to cover most everyday scenarios, with the peace of mind of a live, funded, open-source project.
All in all, Zed combines native speed, real collaboration, AI integration, extensibility, and a declarative setup that appeals to people who want granular control without wasting time. If your workflow fits with those ideas, it's very likely to hook you and become your go-to editor for many tasks; and while it still has some rough edges to iron out, its pace of improvement and technical foundation invite you to consider it as one of the more serious proposals in modern editors.