Update to published ACP Rust SDK 5.4.0 (schema crate 1.19.0). Follow the [protocol changes since schema 1.18](https://github.com/agentclientprotocol/agent-client-protocol/compare/v1.18.0...dbff792240171b199b5ad24d01406720ac9e4bd3) for behavior Zed already implements: - Use each parent's `replay_complete` marker to distinguish historical child state and cancel capabilities from current updates. Keep current child updates that arrive before the resume response, but wait for a successful response before sending child controls. Detach descendants when their root closes. - Reply to agent-cancelled v2 permission requests and elicitations with `cancelled` or `cancel`, respectively. Leave background requests and tools alone when cancelling foreground work, and keep accepting agent status updates. - Ignore `pattern` in v2 elicitation forms, but keep validating it in v1 forms. Cursor and fork-at-position UI, retaining history from a failed resume, and automatic keyed prompt resend are out of scope. This PR uses the published SDK and does not depend on an unreleased SDK fix. Release Notes: - N/A
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking discussion)
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
Zed source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked.
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.
Sponsorship
Zed is developed by Zed Industries, Inc., a for-profit company.
If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.