AI answers take a while, especially on bigger tasks: an agent might read files, run commands and write code for several minutes. Over that time connections wobble. You close the laptop lid, walk between rooms, or your phone hops from Wi-Fi to mobile data. Until now, a dropped connection could leave the chat looking frozen even though the AI was still working.
That is fixed. The chat now notices a lost connection, reconnects by itself, and carries on exactly where it stopped.
What happens behind the scenes
Your AI run does not live in your browser. It runs on our servers, and everything it produces is recorded in order as it goes. Your chat is just a window onto that record. This is why closing a tab never stops a run.
When the connection drops, the chat now does three things:
- Notices quickly. If your browser reports that it went offline, the chat knows immediately. If the connection just goes silent, the chat treats twelve seconds without any sign of life as a stall.
- Retries fast. The first retry comes after about a third of a second, the next after a second, then every two seconds. The moment your browser comes back online, or you switch back to the tab, it tries again at once with a fresh sign-in.
- Picks up where it left off. The chat remembers how many events it has already shown and asks the server for everything after that. Nothing is repeated and nothing is missed, so you never get the same paragraph twice.
The status dot
In the header of the AI chat there is a small dot that shows the state of the connection at a glance:
| Dot | What it means |
|---|---|
| Grey | Idle: nothing is running. |
| Green, glowing | The AI is working and you are receiving its answer. |
| Orange, pulsing | The connection was lost and the chat is reconnecting. |
| Red | You are offline. The AI keeps working, and the chat resumes when you are back. |
Hover over the dot for the same explanation in words. The dot reacts to your browser going offline or online straight away, so it no longer lags behind your real connection by several seconds.
What you will notice
- Close your laptop in the middle of a long run, open it later, and the chat fills in everything that happened while you were away.
- Walk out of Wi-Fi range on your phone and the dot turns orange, then green again as soon as you have a signal. The answer simply continues.
- The run is kept for a couple of hours, so even a long break does not lose the result.
What it does not do yet
Reconnecting covers an answer that is already in progress. If you press send while you are completely offline, that message cannot reach the server, and the chat does not queue it for later. Sending queued messages once you are back online is something we are considering next.
If you build on a train or on hotel Wi-Fi, this one is for you. Try a demo project and run something long.