Contributing to Zed

Thank you for helping us make Zed better!

All activity in Zed forums is subject to our Code of Conduct. Additionally, contributors must sign our Contributor License Agreement before their contributions can be merged.

Contribution ideas

Zed is a large project with a number of priorities. We spend most of our time working on what we believe the product needs, but we also love working with the community to improve the product in ways we haven't thought of (or had time to get to yet!)

In particular we love PRs that are:

• Fixing or extending the docs.
• Fixing bugs.
• Small enhancements to existing features to make them work for more people (making things work on more platforms/modes/whatever).
• Small extra features, like keybindings or actions you miss from other editors or extensions.
• Part of a Community Program like Let's Git Together.

If you're looking for concrete ideas:

• Triaged bugs with confirmed steps to reproduce.
• Area labels to browse bugs in a specific part of the product you care about (after clicking on an area label, add type:Bug to the search).

Sending changes

The Zed culture values working code and synchronous conversations over long discussion threads.

The best way to get us to take a look at a proposed change is to send a pull request. We will get back to you (though this sometimes takes longer than we'd like, sorry).

Although we will take a look, we tend to only merge about half the PRs that are submitted. If you'd like your PR to have the best chance of being merged:

• Make sure the change is desired: we're always happy to accept bugfixes, but features should be confirmed with us first if you aim to avoid wasted effort. If there isn't already a GitHub issue for your feature with staff confirmation that we want it, start with a GitHub discussion rather than a PR.
• Include a clear description of what you're solving, and why it's important.
• Include tests.
• If it changes the UI, attach screenshots or screen recordings.
• Make the PR about one thing only, e.g. if it's a bugfix, don't add two features and a refactoring on top of that.
• Keep AI assistance under your judgement and responsibility: it's unlikely we'll merge a vibe-coded PR that the author doesn't understand.

The internal advice for reviewers is as follows:

• If the fix/feature is obviously great, and the code is great. Hit merge.
• If the fix/feature is obviously great, and the code is nearly great. Send PR comments, or offer to pair to get things perfect.
• If the fix/feature is not obviously great, or the code needs rewriting from scratch. Close the PR with a thank you and some explanation.

If you need more feedback from us: the best way is to be responsive to Github comments, or to offer up time to pair with us.

If you need help deciding how to fix a bug, or finish implementing a feature that we've agreed we want, please open a PR early so we can discuss how to make the change with code in hand.

Things we will (probably) not merge

Although there are few hard and fast rules, typically we don't merge:

• Anything that can be provided by an extension. For example a new language, or theme. For adding themes or support for a new language to Zed, check out our docs on developing extensions.
• New file icons. Zed's default icon theme consists of icons that are hand-designed to fit together in a cohesive manner, please don't submit PRs with off-the-shelf SVGs.
• Features where (in our subjective opinion) the extra complexity isn't worth it for the number of people who will benefit.
• Giant refactorings.
• Non-trivial changes with no tests.
• Stylistic code changes that do not alter any app logic. Reducing allocations, removing .unwrap()s, fixing typos is great; making code "more readable" — maybe not so much.
• Anything that seems AI-generated without understanding the output.

Bird's-eye view of Zed

We suggest you keep the Zed glossary at your side when starting out. It lists and explains some of the structures and terms you will see throughout the codebase.

Zed is made up of several smaller crates - let's go over those you're most likely to interact with:

• gpui is a GPU-accelerated UI framework which provides all of the building blocks for Zed. We recommend familiarizing yourself with the root level GPUI documentation.
• editor contains the core Editor type that drives both the code editor and all various input fields within Zed. It also handles a display layer for LSP features such as Inlay Hints or code completions.
• project manages files and navigation within the filetree. It is also Zed's side of communication with LSP.
• workspace handles local state serialization and groups projects together.
• vim is a thin implementation of Vim workflow over editor.
• lsp handles communication with external LSP server.
• language drives editor's understanding of language - from providing a list of symbols to the syntax map.
• collab is the collaboration server itself, driving the collaboration features such as project sharing.
• rpc defines messages to be exchanged with collaboration server.
• theme defines the theme system and provides a default theme.
• ui is a collection of UI components and common patterns used throughout Zed.
• cli is the CLI crate which invokes the Zed binary.
• zed is where all things come together, and the main entry point for Zed.

Packaging Zed

Check our notes for packaging Zed.