Ben Brandt 12c1fc907f agent: Prompt for always_confirm patterns on in-project file edits (#67037)
`edit_file` and `write_file` skip the permission prompt for files inside
the project whenever the settings decision is `Confirm`. That is
intended for a `confirm` default, where in-project edits are reviewed
after the agent makes them. It also swallowed explicit `always_confirm`
patterns, which the docs say always prompt.

- `authorize_file_edit` now prompts when an `always_confirm` pattern
matches the path. It checks both the raw path and its normalized form,
so a `..` segment can't sidestep a pattern.
- A `confirm` default is unchanged: in-project edits still don't prompt.
- The docs, `default.json` and the `ToolPermissionMode::Confirm` doc
comment described `confirm` as "always prompt". They now describe what
the edit tools do with a `confirm` default and point to `always_confirm`
for prompting on specific files.

Related to #62276. This is an alternative to #66684, which would prompt
on every in-project edit under the default settings.

Release Notes:

- Fixed `always_confirm` patterns for the `edit_file` and `write_file`
agent tools not prompting for files inside the project.
2026-11-16 10:41:11 +00:00
…
…
2026-09-11 09:13:44 +00:00
…
…

Zed

Zed CI

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:

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 specified error for a crate you've created? If so, add publish = false under [package] in your crate's Cargo.toml.
  • Is the error failed to satisfy license requirements for 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 the accepted array in script/licenses/zed-licenses.toml.
  • Is cargo-about unable to find the license for a dependency? If so, add a clarification field at the end of script/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.

S
Description
No description provided
Readme 1.6 GiB
Languages
Rust 95.4%
JSON-with-Comments 2.4%
Python 0.8%
Inno Setup 0.3%
Tree-sitter Query 0.3%
Other 0.4%