Richard Feldman
bd725ced65
When the Agent Panel had the Settings overlay open on top of the ephemeral new-draft thread, pressing **Cmd-N** (or clicking *Start New Thread* in Settings) silently did nothing — the action ran, but the Settings overlay stayed painted on top. The bug was in `AgentPanel::activate_draft`. Every other `activate_*` path goes through `set_base_view`, which clears the overlay. But `activate_draft` has an early return for the case where the base view already holds the requested draft, and that early return only refocused — it never touched `overlay_view`. So when the user was already on the draft and the Settings overlay was on top, "new thread" had nothing visible to do. Fix: in that early-return branch, if an overlay is currently open, clear it (which also handles focusing and emits `ActiveViewChanged`). Added a regression test that puts the panel on the draft, sets the Settings overlay, dispatches `NewThread`, and asserts the overlay is gone. The test directly toggles `set_overlay(OverlayView::Configuration, …)` rather than calling `open_configuration`, because the latter builds provider configuration views and panics on the fake LM provider's `unimplemented!()` `configuration_view` — and the bug being exercised lives entirely in the overlay/base-view bookkeeping. Closes AI-237 Release Notes: - Fixed pressing "New Thread" (or Cmd-N) doing nothing when the Agent Panel's Settings view was open
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.