Richard FeldmanandDanilo Leal
77df6bfef2
Various improvements to settings UI for granular tool permissions, extracted from a larger change: - Add **copy_path** tool to the permissions configuration list - Replace local `RuleType` enum with `ToolPermissionMode` from the settings crate - Improve rule summary display: singular "1 rule" instead of always "1 rules", show invalid pattern count - Add **terminal command parsing preview** — uses `extract_commands` to split chained commands (`&&`, `||`, `;`) so the preview matches the real permission engine's behavior - Add **verdict label** showing the authoritative permission decision (Allow/Deny/Confirm) - Log disagreements between the pattern preview and the engine's authoritative verdict - Display **invalid regex patterns section** with compilation error details - Add regex validation error banner (dismissible) on tool config pages - Add **compile-time validated** `tool_index` for macro-generated render functions (fails to compile if a tool ID is misspelled) - Update move_path/copy_path regex explanations for multi-input tools - Add test validating all tools have `ToolInfo` entries or are in the exclusion list - Add `clear_on_confirm()` — clears the input after confirming (used for "add pattern" inputs) - Add editor reconciliation fix — when settings change externally (e.g. editing settings.json), syncs the cached editor text when not focused - Rename "Configure Tool Rules" → "Tool Permissions" in the settings sidebar - Update description text - Add `regex_validation_error` field to `SettingsWindow` (cleared on page navigation) (No release notes because granular tool permissions are behind a feature flag.) Release Notes: - N/A --------- Co-authored-by: Danilo Leal <daniloleal09@gmail.com>
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.