Chat replies now stream into the thread as Babbily produces them. Before this, a thread filled in steps while it waited for the next update, so the opening words took longer to land.
In our testing across a batch of more than 30 responses, replies began arriving about 47% sooner. How much faster your own chats feel depends on the model, the prompt, the tools a reply uses, and your connection.
Interrupted delivery recovers on its own. If the stream stalls or your connection drops, Babbily reconnects to the reply already in progress rather than starting a second one, so you do not get a duplicate answer.
Stop keeps what you already have. Choose Stop and the partial reply stays in the thread, including the text, reasoning, citations, and media produced so far. Stop also works in the moment right after you send, before any text appears. Stop a reply.
A stopped or stale thread cannot disturb a newer one. Stopping a reply, or a late update from a thread you have moved on from, no longer affects the conversation you are in now.
Now documented: replies keep running when you leave. Babbily has always generated replies on its servers rather than in your browser tab, so closing the tab does not cancel them. That behavior is unchanged, and it is now written down. Leave a reply running.