agent: End turn at message boundary when queue has pending messages#46980
Merged
mikayla-maki merged 1 commit intomainfrom Jan 16, 2026
Merged
agent: End turn at message boundary when queue has pending messages#46980mikayla-maki merged 1 commit intomainfrom
mikayla-maki merged 1 commit intomainfrom
Conversation
Move message queue ownership from ThreadView to Thread, making the queue part of the core data model rather than view state. When the agent is running and a user queues a message, the turn now ends at the next valid boundary (after tool calls complete) instead of waiting for the full generation to finish. This allows queued messages to be sent sooner. The "one turn = one user message" invariant is maintained - the turn ends cleanly and the UI sends the queued message as a new turn. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This feature cost $12
Release Notes: