Eric Holk
032e76cc7e
When a project mixes main repo worktrees (e.g. `extensions`) with linked git worktrees (e.g. `zed4`, a linked worktree of `zed`), two things were broken: 1. **Threads appeared under the wrong sidebar heading.** A thread created in a workspace with both `extensions` and `zed4` would show under the "zed" group instead of the "extensions, zed" group. This happened because `main_worktree_paths` in `ThreadMetadata` was only populated with paths from linked worktrees, omitting regular repos entirely. The fix uses `project_group_key()` to normalize all visible worktrees to their main repo paths — the same normalization the sidebar uses for group headers. 2. **The worktree chip tooltip only showed linked worktree paths**, missing main repo paths like `extensions`. This happened because `worktree_info_from_thread_paths` filtered out main worktree paths entirely. The fix introduces a `WorktreeKind` enum (`Main` / `Linked`) on `ThreadItemWorktreeInfo`, so all worktrees are included in the data model. Chips still only render for `Linked` worktrees (main worktrees are redundant with the group header), but the tooltip now shows all paths. Release Notes: - N/A
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.