Skip to content

message is partially implemented #288

@goyaljiiiiii

Description

@goyaljiiiiii

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions