How to prevent double message rendering when calling tool?

[ramidecodes]

I currently have a tool that calls Replicate to generate an image and returns the URL of the generated image.
On the client side, a simple conditional that checks for toolInvocations renders an Image. This works great.
The problem is that immediately after rendering this, the assistant generates a second message with a little phrase plus the Image result from the tool call rendered again. -__-

Is there any way to prevent the generation of further assistant messages if I've confirmed that the tool call was successful and the generated assets has been rendered with a custom component?

I was flowing a similar approach as the initial Weather tool, returning some structured data and rendering on the client with a nice component. But since I'm returning an image URL the intermediate step of the agent reasoning with the tool response seems to be auto generating the Image as the response using Markdown (I'm parsing message content with a MD component). I feel reluctant to use a prompt-based solution where I indicate the system "not to render image URLs with Markdown". Since it doesn't solve the actual problem of preventing further messages after a given signal.

Thanks!

[lgrammel]

This is currently a limitation of the useChat hook, you can solve it by aggregating consecutive messages into blocks using your own data structure. We plan to overhaul how chat works in the future.

[ramidecodes]

The chat hook is great, good to hear it has more potential!

Could you elaborate more on your suggestion of aggregating messages? I didn't fully get it.

Thanks again.

[lukkoro]

@ramidecodes Have you perhaps resolved this issue?

[ramidecodes]

I haven't come back to this issue actually. But the latest version of the SDK gives you more visibility on the tool calling, so I'm probably going to use some of those new options that are now exposed.
Will report back when I get it fully working.