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
conversations.run_async silently drops typed input entries such as MessageInputEntry #640
client.beta.conversations.run_async and run_stream_async accept inputs as a string or as a list of input entries (ConversationInputs). When the list contains SDK model instances, only FunctionResultEntry objects are kept. Every other entry type (MessageInputEntry, MessageOutputEntry, FunctionCallEntry, ToolExecutionEntry, AgentHandoffEntry) is discarded without any error, so the request is sent with those entries missing. With a single MessageInputEntry the conversation is started with inputs: [].
Dicts with the same content work, which makes this easy to miss.
What should happen
Typed entries should be forwarded exactly like their dict equivalents, in the order given.
There is no branch for the other members of InputEntries, so they fall through and are dropped. The same list is also stored as RunResult.input_entries, so run_result.entries is incomplete as well.
Activity