Approval requests in background runs survive server updates
When a /goal run, Ultracode or a sub-agent is waiting for you to approve a command and the server is updated, the request now stays open. You answer it as usual, and the run continues on the new worker.
If you approve commands for /goal, Ultracode or sub-agents, a server update no longer pauses the run while a request is open. No action needed.
Background runs ask before they run a command, write a file or touch the vault, depending on the approval level of the chat. Until today a server update during such a request was a problem. The old worker waited for your answer until its five minutes were up, then stopped, and the run paused until you confirmed it again.
Text version
When an update starts while a background run waits for your approval, the old worker saves the turn and hands it over. The request stays open with its original deadline. The new worker shows the same request, takes your answer and continues the turn at that command. The model call before it is not bought again, and the command runs at most once.
What changed
An answer you give while the run moves between workers counts. A request you rejected stays rejected, even if you switch the chat to automatic afterwards.
Pressing Stop closes the open request. An answer after the five-minute deadline is no longer accepted.
Prices and plans did not change.