Danilo Leal
8e786bcd87
This PR makes queueing a prompt the default behavior when sending a new one while there's an on-going generation. You can still send a prompt that will immediately interrupt the agent with the `cmd-shift-enter` keybinding, though, which preserves the current behavior. The main motivation for this change is to make the queueing not only more discoverable, but more useful as well, as we're parting from the assumption that most of the time, what you want is to queue it as opposed to interrupting it (even though it's still possible to do either through the keybinding I mentioned above or simply by stopping the generation and sending a new one). Here's a quick video: https://github.com/user-attachments/assets/37f92433-70ef-459f-98ff-41ed80e3e43f In the video, I show sending one prompt and then sending two others that fall straight into the queue. Then, in the middle of the generation of my first prompt, I use the `cmd-shift-enter` keybinding to send a prompt immediately, interrupting the agent, effectively being sent in front of the queue. Release Notes: - Agent: Made queueing prompts the default behavior when sending them while there's an on-going generation.
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.