A Guth Labs publication ↗
Back to News

Cloudflare expands agent-hosting examples, with recovery limits developers need to check

Cloudflare has published new routes for running coding agents on its infrastructure, covering Codex, Exo and Nanocode. The November 9 announcements focus on keeping conversations and work recoverable when a connection or process is interrupted, rather than requiring a developer’s laptop to remain the permanent host. Cloudflare changelog

The Codex announcement describes an experimental WebAssembly adaptation of Rust turn-processing code inside a Durable Object. Its Agents SDK components record completed model and tool results, store conversation history, replay streamed events and maintain a persistent workspace. Completed steps can reuse saved results; interrupted steps may run again. Codex announcement

The current Codex guide, rechecked November 15, documents a different container-based arrangement. The Codex CLI owns its normal tools and session format, while a Durable Object stores session records and reconnects to a running container. A separate egress component supplies model credentials outside the container. The distinction matters: developers should follow the recovery rules for the implementation they actually deploy, not assume the older WebAssembly example and newer container guide behave identically. Current Codex guide

In the container design, a lost container can leave a turn unanswered, and files changed since the last snapshot can disappear. Retrying a turn is an explicit option appropriate only when repeating its effects is safe. The guide also warns that the agent can read the container and that routes require authentication. The API remains experimental. Current Codex guide

Exo separates conversation coordination in Durable Objects from Linux-tool execution in Cloudflare Sandboxes. Its adapter is maintained independently by the Exo project and does not require the Agents SDK. Exo announcement

Nanocode takes another route: a Rust engine compiled to WebAssembly, with progress and tool results saved in SQLite and alarms used to resume work. Its host is likewise independently maintained. Nanocode announcement

Together, the examples offer more hosting choices. They do not remove the need to decide which actions can safely be repeated, where important files persist, or who is allowed to start an agent.

Sources

Sources and citations

Revision history

Published .