"Is it stuck?"
The same tester who caught the memory bug in Part 2 found the next problem, and this one was harder to explain. She asked the e-commerce agent: "Can I return the blue jacket from my last order, and what does the return policy say?"
That question needs two tool calls. The order lookup tool runs, the policy tool runs, then the model writes a long answer with the jacket details, the order number, and the policy steps. On my setup that whole round trip took about ten seconds. For nine of those seconds, the screen showed nothing.
The agent was not stuck. The model was working the whole time. But a silent nine-second wait reads as broken, no matter how good the final answer is. I told her to wait, the text appeared, and she moved on. Every user after her did not get that instruction.
That is the gap this part of the series closes. Same agent, same tools, same memory from Parts 1 and 2. The only change is how the response travels: instead of one string arriving when the answer is complete, tokens reach the browser as the model produces them.
