SOURCE

Your agent needs a computer, not a container — introducing @cloudflare/computer

Properties1
tagscloudflare, agents, runtime, sandbox, primary-source

2 min read

Introducing @cloudflare/computer

Summary

@cloudflare/computer is an open-source early preview of a common workspace and execution abstraction for agents. Instead of assigning every agent a permanently running container, it gives an agent a durable virtual filesystem and lets the runtime select among execution backends. Lightweight file manipulation and JavaScript-oriented work can run in fast isolates; jobs requiring Linux, native binaries, package managers, or test runners can invoke an attached Cloudflare Container. Both operate against synchronized workspace files.

The underlying workspace is backed by SQLite and can be populated from source control, storage buckets, or other files. It exposes filesystem, Git, and shell operations directly and through AI SDK-compatible tools. Cloudflare emphasizes that operations are gated, audited, and observed, providing control over what an agent may change and a paper trail of its actions. Durable Objects host the agent harness and state, while containers become an on-demand vertical-scaling tool rather than the default unit for every run.

This is directionally useful to the proof-business plan because evidence-producing work often combines cheap parsing, file/report generation, and occasional heavier browser or native-tool execution. A shared workspace also creates a natural place to assemble a client receipt before publication. But the product is explicitly an early preview built to learn with advanced customers. It is not needed to validate Mystery-Shopper Receipts or AI-Visibility Audits; a smaller local or existing Worker/browser implementation should come first. The strategic lesson to keep is workload-tiering and auditable workspaces, not a mandate to adopt this package immediately.

Key Claims

  • One workspace can span isolate and container execution backends.
  • The durable filesystem can be seeded from repositories, buckets, or arbitrary files.
  • Agent tools include read, write, edit, list, Git, and execution operations.
  • Operations are intended to be gated, audited, and observed.
  • The release is an open-source early preview, not a mature general-availability product.

Connections

Contradictions

  • None. It lowers the adoption priority implied by the roundup by making the early-preview status explicit.