Why the wait

Sometimes your agent
needs a moment.

Ask for something that needs the internet, a file, or a bit of arithmetic, and your agent goes off and does it. That can take a few seconds, sometimes more. So Yokwi holds the mic, sweats a little, and, when your agent reports its steps, shows you what it is doing while you wait. Quiet does not by itself mean broken. The window below is a scripted illustration.

Ready
your agent0.0s
ThinkingA second or two

Plain questions and quick replies. The loop coils forward, the little dots rise, and the answer follows almost at once.

Using a toolThree to ten seconds, sometimes more

A web search, reading a file, running some code. When your agent reports its steps, each one shows up in the window with how long it took; otherwise you see the thinking loop until the reply lands. This is your agent working, not Yokwi stalling.

SpeakingRight away

Yokwi reads the separate spoken explanation your agent sends with its answer, starting as soon as its first sentence is ready; the full answer is shown on screen. A text-only answer is shown, not read.

You can talk over it. Start speaking any time and the current reply is dropped so it can listen to the new thing. And if the window has been quiet for more than a minute, check the connection: the support page covers the usual causes. A long wait alone does not prove something failed.