You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Queued prompts can start before the active response finishes #28375
When a prompt is submitted while a session is already running, the queued prompt can be picked up by the active loop before the active assistant response has completed.
This breaks the expected turn ordering. The intended behavior is:
Active user prompt is sent to the model.
Active assistant response completes.
Queued user prompt is processed.
Queued assistant response completes.
Instead, the queued prompt can be included in the next model input too early, while the first response is still in progress.
Expected behavior
Queued prompts should be persisted and marked as queued, but the queued turn should not be drained into an LLM call until the active prompt loop has finished.
Why this matters
This can cause the model to see future user input before it has finished responding to the current turn, which changes conversation semantics and can produce confusing or out-of-order responses.
This issue might be a duplicate of existing issues. Please check:
Queued prompts dequeued prematurely #15696: "Queued prompts dequeued prematurely" — describes the same core problem: queued prompts are picked up by the active loop before the current response completes, with nearly identical expected behavior (queued turns should not be drained until the active loop finishes).
Activity
rehatkathuria commentedon May 19, 2026
Closing after being told this was intended behaviour.
github-actions commentedon May 19, 2026
This issue might be a duplicate of existing issues. Please check: