mirror of
https://github.com/zed-industries/zed.git
synced 2026-05-24 13:39:08 +00:00
original uri https://github.com/zed-industries/zed
https://zed.dev
f8b74acc0f
Follow-up to the terminal permission params refactor, addressing @benbrandt's [review feedback](https://github.com/zed-industries/zed/pull/51782#pullrequestreview-2926899804) about string formatting leaking into the UI layer. ## Changes ### Outcome construction moved to acp_thread - Added `PermissionOptionChoice::build_outcome(is_allow)` — builds a `SelectedPermissionOutcome` from a choice, attaching `SelectedPermissionParams::Terminal` when the choice carries `sub_patterns`. - Added `PermissionOptions::build_outcome_for_checked_patterns(checked_indices, is_allow)` — handles the `DropdownWithPatterns` per-command checklist flow, returning `None` when zero patterns are checked (degrading to once). The UI's `authorize_with_granularity` no longer does any `format!("always_allow:{}",...)` string formatting or `SelectedPermissionParams` construction. ### `option_kind` folded into `SelectedPermissionOutcome` `SelectedPermissionOutcome` now carries `option_kind: acp::PermissionOptionKind`, eliminating the separate parameter that was threaded through the entire `authorize_tool_call` chain: ``` ThreadView::authorize_tool_call → Conversation::authorize_tool_call → AcpThread::authorize_tool_call ``` Every signature in this chain dropped one parameter. ### `SelectedPermissionParams` removed from UI imports The type is now only referenced by `acp_thread` (construction) and `agent` (consumption). The UI passes `SelectedPermissionOutcome` opaquely. Release Notes: - N/A |
||
|---|---|---|
| .cargo | ||
| .cloudflare | ||
| .config | ||
| .factory | ||
| .github | ||
| .zed | ||
| assets | ||
| ci | ||
| crates | ||
| docs | ||
| extensions | ||
| legal | ||
| nix | ||
| script | ||
| tooling | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .prettierrc | ||
| .rules | ||
| AGENTS.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CLAUDE.md | ||
| clippy.toml | ||
| CODE_OF_CONDUCT.md | ||
| compose.yml | ||
| CONTRIBUTING.md | ||
| debug.plist | ||
| default.nix | ||
| Dockerfile-collab | ||
| Dockerfile-collab.dockerignore | ||
| Dockerfile-cross.dockerignore | ||
| Dockerfile-distros | ||
| Dockerfile-distros.dockerignore | ||
| flake.lock | ||
| flake.nix | ||
| GEMINI.md | ||
| LICENSE-AGPL | ||
| LICENSE-APACHE | ||
| LICENSE-GPL | ||
| livekit.yaml | ||
| lychee.toml | ||
| Procfile | ||
| Procfile.all | ||
| Procfile.web | ||
| README.md | ||
| renovate.json | ||
| REVIEWERS.conl | ||
| rust-toolchain.toml | ||
| rustfmt.toml | ||
| shell.nix | ||
| typos.toml | ||
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.