Queued prompts dequeued prematurely #15696

Overview

When the plan/ build agent is still running in response to a prompt and the user queues one or more new prompts, subsequent prompts incorrectly get pulled at once before the on going response fully completes (apparently soon as the agent pauses for a tool call).

The agent often immediately acknowledges subsequent prompts (as reflected in its thinking block), but then either proceeds to complete the original response and inconsistently handles or forgets later ones OR starts responding to some or all of the newer prompts without completing its response for the previous (the model in use seems to affect the consistency here).

Steps to reproduce

1. Start with a prompt that will trigger some tool calls.
2. Before the agent completes all necessary tool calls to finish responding, queue couple of more prompts.

Expected behavior

Queued prompts should be handled one after the other in the correct order once the in progress work is completed and the initial prompt is full handled.

Alternatively,

• User intent for queued prompts on processing order/ priority (wait for the on going response to complete or not..., dequeue all at once or one by one... etc.) is captured and handled accordingly.
• Or the last queued prompt consistently disrupt the current loop at the next immediate chance and takes priority over work in progress/ any previously queued prompts. This however means queueing to run sequentially is either unsupported or addressed separately (drafts feature?).

Actual behavior

Queued prompts run as soon as the previous prompt loop exits for a tool call. Then either the original prompt or the subsequent ones are responded, sometimes both, not in a consistent manner.

Note: When multiple prompts are queued, they ALL run at once at the next tool call pause.

Environment

• Version: OpenCode 1.2.15
• Clients: TUI, Web UI