Danilo Leal
589e2c0fe4
Closes https://github.com/zed-industries/zed/issues/37660 This PR makes sections in the AI settings UI more consistent with each other and also just overall simpler. One of the main changes here is adding the tools from a given MCP server in a modal (as opposed to in a disclosure within the settings view). That's mostly an artifact of wanting to make all of the items within sections look more of the same. Then, in the process of doing so, also changed the logic that we were using to display MCP servers; previously, in the case of extension-based servers, we were only showing those that were _configured_, which felt wrong because you should be able to see everything you have _installed_, despite of its status (configured or not). However, there's still a bit of a bug (to be solved in a follow-up PR), which already existed but it was just not visible given we'd only display configured servers: an MCP server installed through an extension stays as a "custom server" until it is configured. If you don't configure it, you can't also uninstall it from the settings view (though it is possible to do so via the extensions UI). Release Notes: - agent: Improve settings view UI and solve issue where MCP servers would get unsorted upon turning them on and off (they're all alphabetically sorted now).
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.