Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Find a file
2024-07-11 11:15:49 -04:00
.cargo
.cloudflare
.config
.github Build x86 linux too :/ (#14068) 2024-07-10 11:04:32 -06:00
.zed
assets Add Upper/LowerCase binds to Linux Sublime Text keybinds (#14155) 2024-07-11 11:15:49 -04:00
crates Allow Zed Nightly to use v0.0.7 of the Zed extension API (#14209) 2024-07-11 10:54:15 -04:00
docs docs: Add stray design tweaks (#14205) 2024-07-11 11:57:22 -03:00
extensions dart: Release 0.0.3 (#14176) 2024-07-11 11:48:04 +02:00
script AlpineLinux: Fix install.sh and docs typo (#14105) 2024-07-10 17:41:43 -04:00
tooling/xtask
.dockerignore
.git-blame-ignore-revs Ignore whitespace commits (#13889) 2024-07-11 02:45:40 -04:00
.gitattributes
.gitignore
.mailmap
Cargo.lock dart: Release 0.0.3 (#14176) 2024-07-11 11:48:04 +02:00
Cargo.toml chore: Clippy fixes for 1.80 (#13987) 2024-07-10 17:53:17 +02:00
CODE_OF_CONDUCT.md
compose.yml
CONTRIBUTING.md
debug.plist
docker-compose.sql
Dockerfile
flake.lock
flake.nix
LICENSE-AGPL
LICENSE-APACHE
LICENSE-GPL
livekit.yaml
Procfile
README.md
rust-toolchain.toml
shell.nix
typos.toml

Zed

CI

Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.


Installation

Packaging status

On macOS and Linux you can download Zed directly or install Zed via your local package manager.

Other platforms are not yet available:

Developing Zed

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 specified error for a crate you've created? If so, add publish = false under [package] in your crate's Cargo.toml.
  • Is the error failed to satisfy license requirements for 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 the accepted array in script/licenses/zed-licenses.toml.
  • Is cargo-about unable to find the license for a dependency? If so, add a clarification field at the end of script/licenses/zed-licenses.toml, as specified in the cargo-about book.