Skip to content

Queued prompts can start before the active response finishes #28375

Closed

Description

@rehatkathuria

Description

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:

  1. Active user prompt is sent to the model.
  2. Active assistant response completes.
  3. Queued user prompt is processed.
  4. 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.

Activity

  1. rehatkathuria commented on May 19, 2026

    @rehatkathuria
    Author

    Closing after being told this was intended behaviour.

  2. github-actions commented on May 19, 2026

    @github-actions
    Contributor

    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).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions