Skip to content

agent_ui: Queue prompts by default when sending them while generating#46797

Merged
danilo-leal merged 3 commits intomainfrom
queue-by-default-when-generating
Jan 14, 2026
Merged

agent_ui: Queue prompts by default when sending them while generating#46797
danilo-leal merged 3 commits intomainfrom
queue-by-default-when-generating

Conversation

@danilo-leal
Copy link
Member

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:

Screenshot.2026-01-14.at.10.48.mp4

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.

@cla-bot cla-bot bot added the cla-signed The user has signed the Contributor License Agreement label Jan 14, 2026
@danilo-leal danilo-leal merged commit 9621fac into main Jan 14, 2026
23 checks passed
@danilo-leal danilo-leal deleted the queue-by-default-when-generating branch January 14, 2026 16:12
rtfeldman pushed a commit that referenced this pull request Jan 14, 2026
…#46797)

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.
danilo-leal added a commit that referenced this pull request Jan 15, 2026
Follow up to #46797

When you send a message, as per the PR linked above, Zed will now queue
it by default. But if you want to fast-track it/interrupt the agent
immediately, effectively sending the first message in the queue, you can
just hit enter again and it will get sent right away.


https://github.com/user-attachments/assets/5e6230f6-c56e-4496-9bcb-8d6ffb9e19cb

Release Notes:

- Agent: Made it easier to interrupt the agent while having messages in
the queue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed The user has signed the Contributor License Agreement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant