Cloudflare Computer adds recovery and approval pauses for agent execution

Cloudflare Computer adds recovery and pauses for approvals during agent execution.

**Dek:** The October 26 update lets workspace code resume after an interruption and wait for an external decision. Application owners still need to reconcile any side effects made outside the runtime.

Cloudflare announced on October 26 that its Computer workspace package can resume code after interruptions and pause a run for an external decision. The changelog documents the behavior from version 0.7.0. Its approval example uses a custom module to interrupt a run before posting a comment and supplies the decision from the surrounding application. The runtime then continues or fails according to that decision. [Cloudflare Computer changelog](https://developers.cloudflare.com/changelog/post/2026-10-26-computer-durable-javascript/)

What a durable pause gives the application

A tool call can be easy to express and still have consequences that need a human decision. A project agent might prepare a comment, a deployment or a change to an external record. Pausing lets the application retain the pending operation while someone reviews it. A useful approval presents the actual target and proposed action, so the reviewer can distinguish one change from another. The application still decides which identity can approve it and whether a decision remains valid after the proposal changes. [Cloudflare Computer changelog](https://developers.cloudflare.com/changelog/post/2026-10-26-computer-durable-javascript/)

Recovery addresses a different case. An interruption can occur because a process restarts or an application deploys while code is in progress. The workspace runtime can preserve execution across that event. If the code has already reached an external service, the application still needs a way to determine what happened there. A timeout after a request can leave the outcome uncertain. Repeating the request without reconciling the original can duplicate an action even when the local run has durable state.

How to verify recovery without duplicating work

Exercise an approval path with an authorized reviewer and a separate rejection path. Capture the proposed action before the interruption and verify it is the one the resumed run uses. For an external write, simulate a request whose result is lost and verify that the application can look up the original operation or safely use its original request identity. Testing these as separate cases makes it easier to see whether the problem is in the runtime’s recovery, the application’s approval gate or the external service’s response.

Cloudflare’s update gives developers a place to suspend long-running agent code without holding a synchronous request open for the entire review. Reliable operation still depends on the records the application keeps at the boundaries it controls.