Danilo Leal
9741e9ab8b
Closes https://github.com/zed-industries/zed/issues/39183 This PR adds UI improvements to clarify the concept of "default rules" and how they separate from regular rules. This is mostly motivated by the issue linked above, where it clarified that the star icon was communicating a "favoriting" affordance, which is not correct with how rules work in Zed. When you tag/attach a rule as default, it will always be included in every prompt, together with the agent's system prompt and project rules (if they exist). Hopefully, this will make understanding better. Here's how it looks like now? https://github.com/user-attachments/assets/435d3af7-e8a6-4646-8f00-94a409bd5f42 Release Notes: - Improve rules library UI to better communicate the concept of default rules vs. regular rules.
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.