How a request runs: waiting, stopping and background work
Every message or approval is one request. One request runs at a time in each conversation. You can stop it, and approved changes keep going even if you close the page.
One request per conversation
If you send a message while the previous request is running, it waits up to 15 seconds. On the web, a new message cancels the normal reply in progress. An approved build isn’t canceled.
A message in another conversation doesn’t cancel anything.
Stopping
The stop button works from the moment the thinking indicator shows. Only the person who started the request can stop it.
Running in the background
Approved changes, builds and documents keep going if you close the tab, and you can follow them from another tab. A normal reply stops if your connection drops.
The thinking panel
The thinking steps show for large requests only: a build plan, a document design, or comparisons and breakdowns.
Safe resending
If your app resends the same message after a dropped connection, it isn’t done or charged twice.
If something goes wrong
A real example
The manager approved a large build, then closed his computer.
- He opened the assistant from his phone a few minutes later.
He found the build finished, with its summary in the same conversation.