Currently only those invited from the waitlist can download Zed. You must either be invited from the Waitlist or be invited by an Insider. We are constantly adding waves of new Insiders from our waitlist, so hang tight! Adding people in groups allows us to continually get feedback as we develop Zed so we can build the best editor possible.
We currently don't offer a convenient way for users to log out of GitHub from within Zed. If you'd like to log out, follow these steps:
- Open the
- In the
loginkeychain, find and delete the
- Restart Zed
We're focusing on a single platform for now because we're a small team. At our current scale, maintaining additional platforms would represent a big cost without much additional learning. We plan to support Linux and Windows before 1.0, and to support a web version some time after that.
Any news will be posted to our platform-tracking issues.
The last 1000 lines of Zed's log file can be opened in a Zed buffer by searching for
zed: open log within the command palette. If you need to view more history, you can find the full log file at
We stopped working on Atom and started on the foundations of Zed when we realized that we couldn't shape Atom into our vision for the ultimate editor. While we respect and appreciate the innovations brought by Visual Studio Code, we never found ourselves loving it enough to give up on the dream. Ultimately, we think we're going to add the most value to the world by creating something new. It's also a lot more fun.
As the last letter of the alphabet, Zed symbolizes the ultimate in our pursuit of building the perfect editor. This is the tool we've always envisioned using, and we believe it to be the last one we will build.
We plan to make Zed extensible via WebAssembly, but we're taking a different approach than we did with Atom. Our goal is to make Zed fast, stable, and collaborative first, extensible second. We'll be taking a more conservative approach with our APIs to ensure we can preserve our core values even as users add extensions.
Yes. Zed will be free to use as a standalone editor. We will instead charge a subscription for optional features targeting teams and collaboration.
We'd like to be as open as possible while maintaining the ability to run a profitable business. This probably means some kind of "open core" model, where the editor is available under the GPL but other parts of our system remain proprietary. The timeline and exact strategy are still uncertain at this stage.
This isn't something we're worrying too much about right now, but we anticipate adding enterprise-focused features eventually.