08c594966f
This commit introduces HTTP and SSE transport implementations for the `context_server` crate, allowing Zed to communicate with remote context providers. The new transports are built on the existing `http_client` and `gpui` executor, adhering to the project's architectural patterns. To support configuration of these new transports, the settings system has been updated: - A `Remote` variant has been added to the `ContextServerSettings` enum, allowing users to configure remote servers in `settings.json` with a URL. - The project logic has been updated to initialize remote context servers using the new `ContextServer::from_url` constructor. - The agent configuration UI now includes an "Add Remote Server" option and a dedicated modal for adding and editing remote server configurations. Unit tests have been added for the new transports and for the logic that handles remote server configurations.
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.