Dijana Pavlovic
ade0f1342c
Closes #41458 Dynamically position mode selector tooltip to prevent clipping. Position tooltip on the right when panel is docked left, otherwise on the left. This ensures the tooltip remains visible regardless of panel position. **Note:** The tooltip currently vertically aligns with the bottom of the menu rather than individual items. Would be great if it can be aligned with the option it explains. But this doesn't seem trivial to me to implement and not sure if it's important enough atm? Before: <img width="431" height="248" alt="Screenshot 2025-10-30 at 22 21 09" src="https://github.com/user-attachments/assets/073f5440-b1bf-420b-b12f-558928b627f1" /> After: <img width="632" height="158" alt="Screenshot 2025-10-30 at 17 26 52" src="https://github.com/user-attachments/assets/e999e390-bf23-435e-9df0-3126dbc14ecb" /> <img width="685" height="175" alt="Screenshot 2025-10-30 at 17 27 15" src="https://github.com/user-attachments/assets/84efca94-7920-474b-bcf8-062c7b59a812" /> Release Notes: - Improved the agent panel's mode selector by preventing it to go off-screen in case the panel is docked to the left.
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.
Other platforms are not yet available:
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
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.