MartinYe1234
da7945aeae
Edits targeting the agent skills directory (project `.agents/skills/` and global `~/.agents/skills/`) always prompt regardless of permission settings, because they route through `authorize_always_prompt` which never consults the persisted `always_allow` rules. The permission prompt still rendered an "Always allow" button, though. Clicking it wrote an `always_allow` rule into settings that was then silently ignored on the next skills edit, so users were re-prompted every time despite having chosen "always allow" — exactly the confusion reported in AI-346. This keeps the always-prompt behavior intact and just hides the misleading "Always allow" / "Always deny" options for skills, leaving once-only Allow/Deny. Applies to all mutating skills tools: `edit_file`, `write_file`, `copy_path`, `move_path`, `delete_path`, and `create_directory`. Implementation: - New `ToolPermissionScope::AgentSkills`, set via `ToolPermissionContext::for_agent_skills()`. - `build_permission_options` returns flat once-only Allow/Deny for that scope (mirrors the existing `SymlinkTarget` handling). - Wired into both authorization entry points (`authorize_file_edit` and `authorize_with_sensitive_settings`). - Tests assert no `AllowAlways` option is offered for each affected tool. Settings-file prompts (`.zed/settings.json`, global config) are intentionally left unchanged. Closes AI-346 Release Notes: - Removed the misleading "Always allow" button from agent permission prompts for edits to the agent skills directory, since those edits always require confirmation.
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.