How to Configure Queued Messages
💬 Conversation
With queued messages on, the turn reads the conversation's inbox before each model call, so a message the user sends while the agent works reaches it between two tool calls instead of waiting for the next turn. The message's text, images and attached documents reach the agent as they would at the start of a turn, and the streamed answer marks where it was read with a user_message content part. The API flow is in Sending to a Conversation.
The provider runs only in an interactive, stateful turn: without an inbox it is off. In the agent editor the provider is the Queued messages group.
Configuration​
{
"queued_messages_provider_configuration": { "enabled": true },
"mid_turn_queued_messages_source_configuration": { "enabled": true }
}
| Setting | Type | Default | Description |
|---|---|---|---|
enabled | bool | false | Read the messages the user sends while a turn runs before the model's next call. Off, they wait for the next turn. |
include_sources / exclude_sources | list | unset | Source filtering, as on every provider |
Sources​
| Source | Default | Description |
|---|---|---|
mid_turn | disabled | Gives the model each message sent while the turn runs as guidance for the task in progress, so it continues instead of ending the turn early |
mid_turn_queued_messages_source_configuration:
| Setting | Type | Default | Description |
|---|---|---|---|
enabled | bool | false | Switch the source on |
wording | str | built-in | How the message reaches the model; {message} is replaced by its text |