I was testing the message, and it feels unfinished.
Compared to the message, the flow is different in a few important ways. Task state updates don’t always line up the same, error handling feels inconsistent, and streaming responses can get weird when a client disconnects or the stream fails partway through.
Can we make message/stream follow the same lifecycle as normal tasks (submitted > working > completed/failed/cancelled)
I was testing the message, and it feels unfinished.
Compared to the message, the flow is different in a few important ways. Task state updates don’t always line up the same, error handling feels inconsistent, and streaming responses can get weird when a client disconnects or the stream fails partway through.
Can we make message/stream follow the same lifecycle as normal tasks (submitted > working > completed/failed/cancelled)