67e41996be
When the agent issued several parallel tool calls that all required confirmation, clicking "Always for en.wikipedia.org" (or similar) on the first prompt would persist the new rule to settings but leave the sibling prompts stuck waiting on their own oneshot channels. The same happened across subagents, and whenever the user edited settings.json by hand while prompts were on screen. `ToolCallEventStream::authorize()` now takes full ownership of the permission decision. It evaluates the tool-permission settings up front, and on Confirm it spawns a task that races the user's response against a `SettingsStore` observer. When settings change, it re-runs the decision; a new Allow or Deny drops the response receiver, flips the tool call status to dismiss the prompt UI, and resolves the task without user input. Subagents fall out of this for free since each thread observes `SettingsStore` independently. A few tools (`copy_path`, `move_path`, `delete_path`, `create_directory`, `save_file`, `restore_file_from_disk`, and the `edit-file` helper) sometimes need to prompt even when settings say Allow — for example, edits that target `.zed/settings.json`. For those, a new `authorize_always_prompt()` method skips the settings check and always waits for user input; tools pick between the two at the call site based on whether the path is sensitive. Closes #54101. Release Notes: - In the agent panel, when you click "Always allow" for a tool, this decision now gets propagated to other pending calls to the same tool. Co-authored-by: Ben Brandt <benjamin.j.brandt@gmail.com> Co-authored-by: Bennet Bo Fenner <bennetbo@gmx.de>
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 issue)
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
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.