Long-running replies no longer get cut off early

Chat replies that run a long command or wait for your approval were sometimes stopped too soon. The waiting limits now depend on what the reply is doing.

Over ten days we counted 19 chat replies that stopped with "send your message once more". The server cuts a reply off when it hears nothing for a while, so a stuck reply does not hang forever. In most of these cases nothing was stuck. The limit was simply too short for the work.

What changed

Commands the model runs in your workspace, such as a build or a package install, can take up to ten minutes and only report back when they finish. While one is running, the reply now waits up to eleven minutes instead of about three.
Models that think before they write get a little longer too. If the model itself never starts, you now get a clear message saying so, not the generic cut-off.
When a tool needs your approval and you do not answer within five minutes, the model no longer asks again and again until the 30-minute limit ends the reply. It skips the other approval requests for that reply and wraps up.
Once you approve a tool, the chat shows it as running. Before, it could still look like it was waiting for you, including after a page reload.
The error text now says whether a tool gave no result or the model went quiet.

What stays the same

A single reply still ends after 30 minutes. That limit stops a model from looping through tools without end.