Overview
Cloudflare Computer centers agent work on a SQLite-backed Workspace owned by a Durable Object, then surrounds that durable state with Worker shells, Worker JavaScript, or a container mirror for different execution needs. The series moves from filesystem representation and chunked persistence to push–pull synchronization, cursors, replay boundaries, and failure recovery, then applies those models to tools, Git, mounts, artifacts, and publication. Its value is strongest for inspectable, agent-scale working sets with deliberate capability choices; fixed-chunk and FUSE costs, last-writer-wins behavior, lifecycle gaps, and preview status limit claims about throughput, collaboration, and production readiness.
Learning outcomes
- The Durable Object’s SQLite-backed Workspace is authoritative; a container mirror becomes authoritative only after synchronization applies its changes.
- Fixed 512 KiB chunks, content hashes, tombstones, and cursors make transfers selective and restartable, not semantically merged.
- Choose Worker shell for supported text work, Worker JavaScript for bounded structured modules, and containers for real Linux requirements.
- Cloudflare Computer is a preview fit for inspectable agent working sets, not a promise of high-throughput storage, automatic conflict resolution, or production readiness.
Keywords
Preview every chapter · Unlock full text, audio, and video from chapter 4
PlansFAQ
Where does Cloudflare Computer store an agent’s durable files?
Cloudflare Computer stores an agent’s authoritative files in a SQLite-backed Workspace owned by a Durable Object. Containers use a mirror, while Worker backends access the host store more directly.
Which Cloudflare Computer runtime should an agent use?
An agent should use the smallest backend that meets the task: Worker shell for supported text, Worker JavaScript for bounded structured modules, and container shell for full Linux. Host policy must still control access.
Are Cloudflare Computer container writes automatically durable?
No, a container write becomes authoritative only after the post-command pull applies it to the Durable Object’s Workspace. An unsynced write can be lost if the container fails, while a pending pull can resume without rerunning the command.
Does Cloudflare Computer resolve concurrent edits?
No, its synchronization converges on last-writer-wins state rather than merging independent file intentions. Use one active writer, separate subtrees, or an explicit handoff for shared work.