Zed Improved. Aiming to improve upon Zed and make a truly delightful code editor.
https://zed.dev
7d4d8b8398
(This PR does not add GPT-5 to Zed Pro, but rather adds access if you're using your own OpenAI API key.) <img width="772" height="333" alt="Screenshot 2025-08-07 at 2 23 18 PM" src="https://github.com/user-attachments/assets/42e75082-118a-4737-89b6-a740ae33b169" /> --- **NOTE:** If your API key is not through a verified organization, you may see this error: <img width="549" height="253" alt="Screenshot 2025-08-07 at 2 04 54 PM" src="https://github.com/user-attachments/assets/d0b6d739-9c39-4af3-88d7-0c9609b0e6ba" /> Even if your org is verified, you still may not have access to GPT-5, in which case you could see this error: <img width="543" height="98" alt="Screenshot 2025-08-07 at 2 09 18 PM" src="https://github.com/user-attachments/assets/e3ed31e3-2a11-4f07-8f3c-5b410fbe4540" /> One way to test if you're in this situation is to visit https://platform.openai.com/chat/edit?models=gpt-5 and see if you get the same "you don't have access to GPT-5" error on OpenAI's official playground. It looks like this: <img width="581" height="196" alt="Screenshot 2025-08-07 at 2 15 25 PM" src="https://github.com/user-attachments/assets/ea1454ca-3c10-4703-8126-c02cb92a34f2" /> Release Notes: - Added GPT-5, as well as its mini and nano variants. To use this, you need to have an OpenAI API key configured via the `OPENAI_API_KEY` environment variable. |
||
|---|---|---|
| .cargo | ||
| .cloudflare | ||
| .config | ||
| .github | ||
| .zed | ||
| assets | ||
| crates | ||
| docs | ||
| extensions | ||
| legal | ||
| nix | ||
| script | ||
| tooling | ||
| .clinerules | ||
| .cursorrules | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .prettierrc | ||
| .rules | ||
| .windsurfrules | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CLAUDE.md | ||
| clippy.toml | ||
| CODE_OF_CONDUCT.md | ||
| compose.yml | ||
| CONTRIBUTING.md | ||
| Cross.toml | ||
| debug.plist | ||
| default.nix | ||
| docker-compose.sql | ||
| Dockerfile-collab | ||
| Dockerfile-collab.dockerignore | ||
| Dockerfile-cross | ||
| Dockerfile-cross.dockerignore | ||
| Dockerfile-distros | ||
| Dockerfile-distros.dockerignore | ||
| flake.lock | ||
| flake.nix | ||
| LICENSE-AGPL | ||
| LICENSE-APACHE | ||
| LICENSE-GPL | ||
| livekit.yaml | ||
| lychee.toml | ||
| Procfile | ||
| Procfile.postgrest | ||
| README.md | ||
| renovate.json | ||
| rust-toolchain.toml | ||
| shell.nix | ||
| typos.toml | ||
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.