Updates `agent-client-protocol` to 3.6.0 (schema 1.13) and adopts the protocol clarifications made since schema 1.12. Each commit stands alone: 1. **Update agent-client-protocol to 3.6.0 (schema 1.13)** - Adapts to the new types: tagged `AvailableCommand`, `CancelledPermissionOutcome`, `ClientAuthCapabilities`, 1-based `NonZeroU32` tool call lines, signed terminal exit codes, unsigned `ResourceLink.size`, and v2 `RequestId` (no `null`). - Terminal exit codes keep the platform's signed value instead of `c as u32`; v1 Agents still receive the same 32-bit pattern as before. - Session message participants follow the new patch rules: omitted keeps, `null` clears, a value replaces. - An unknown tool status shows as in progress. - Unknown command kinds are offered as plain commands. - v1 `terminal/*` calls for an unknown terminal return `-32002`. - A `terminal_update` with an invalid `output` snapshot still applies its other fields (agentclientprotocol/agent-client-protocol#2577). 2. **Reject elicitation forms Zed can't render**: `-32602` for a required property of an unknown type, a dangling `required` name, or `enum` with `oneOf`. Optional unknown properties are left out, and defaults that don't match their schema are ignored. 3. **Show streamed tool text as continuous text**: adjacent plain text in `tool_call_content_chunk` extends the previous text block, like message chunks. 4. **Apply tool call permission subjects to the transcript**: a `tool_call` subject is applied like a `tool_call_update` before the prompt is shown, so the permission card attaches to its tool call. Related SDK and spec PRs: agentclientprotocol/rust-sdk#450, agentclientprotocol/rust-sdk#451, agentclientprotocol/agent-client-protocol#2578. 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.