stop works client side, but backend continue to stream

[sam-goodwin]

useAgentChat proxies the underlying useChat's stop function, but does not reflect on the server.

I know this, because if i refresh after stopping the stream, the message appears.

const {
  stop,
  // ..
} = useAgentChat({ .. });

const handleCancel = () => {
  stop();
}

To workaround, I had to create an AbortController and pass the AbortSignal through to streamText:

const result = streamText({
  // ..
  abortSignal: controller.signal,
});

Then, I call my own API on the Agent to trigger the Abort Signal.

The final barrier I haven't yet gotten over is how to make sure the final message parts are persisted.

Not sure if I am approaching this in the right way.

[threepointone]

I'll fix it this week

[threepointone]

question on expected behaviour: do you want to stop the stream midway on the server side, as well as delete the full message itself? or do you expect the message midstream to be persisted? I suspect the former, but checking with you.

[sam-goodwin]

Persist the message.

Then, I'd expect to be able to delete the message as another operation (and ui control).

This would match behavior of tools like Cursor.

[threepointone]

persist the half streamed message? not sure if that's the desired behaviour, would be confusing. I suspect it's better to just reset to the state before the message was sent.

it's also a bit tricky because the response might be changing previous messages as well, especially for human in the loop stuff.