---
title: "Comment by Kartik N V J K on \"Why AI replies stream word-by-word\" | Hashnode"
description: "Your split UTF-8 example has a cousin in streamed tool calls: the arguments arrive as JSON fragments, and parsing per chunk crashes on half-formed objects. I bu"
url: "https://hashnode.com/posts/why-ai-replies-stream-word-by-word/6ac34ccf409651402523c315/comment/6ac54d574e3ae971a15544d5"
---

[Discussion](https://hashnode.com/posts/why-ai-replies-stream-word-by-word/6ac34ccf409651402523c315)

Comment [Why AI replies stream word-by-word](https://hashnode.com/posts/why-ai-replies-stream-word-by-word/6ac34ccf409651402523c315)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Oct 6](https://hashnode.com/posts/why-ai-replies-stream-word-by-word/6ac34ccf409651402523c315/comment/6ac54d574e3ae971a15544d5)

Your split UTF-8 example has a cousin in streamed tool calls: the arguments arrive as JSON fragments, and parsing per chunk crashes on half-formed objects. I buffer the fragments and parse once the stop signal arrives. Does the series cover streamed tool calls?

[Nagappan S](https://hashnode.com/@imkarthik03)

[Oct 13](https://hashnode.com/posts/why-ai-replies-stream-word-by-word/6ac34ccf409651402523c315/comment/6ac54d574e3ae971a15544d5#reply-6acdd272acaf114305c1ac7f)

Buffering until the stop signal is the safe default. If you need to act earlier, an incremental JSON parser that only commits complete values works, but I'd still never execute the call before the arguments validate. It's not in the series yet, so it's a good candidate for a follow-up post. Thanks for the nudge.
