cloudflare/computer

Purpose and Public Entry Points

Cloudflare Computer is a preview TypeScript monorepo for Durable Object–hosted workspaces: an authoritative SQLite-backed virtual filesystem plus pluggable execution runtimes. Consumers primarily use @cloudflare/computer through packages/computer/src/index.ts, construct a Workspace, use filesystem APIs, and invoke workspace.runtime.exec(source, { backend }). The underlying filesystem is independently usable through packages/dofs/src/index.ts.

Workspace Orchestration

@cloudflare/computer is the Durable Object-facing integration layer. It owns Workspace lifecycle, client/proxy boundaries, runtime registration, heartbeat/observation, and the uniform execution interface.

• packages/computer/src/workspace.ts

• packages/computer/src/runtime/runtime.ts

• packages/computer/src/client.ts

Execution is selected by stable backend ID and connected lazily. The uniform runtime boundary hides whether source is shell text or an ECMAScript module.

Authoritative Durable Object Filesystem

@cloudflare/dofs supplies the durable virtual filesystem, backed by Durable Object SQLite. Its filesystem implementation provides POSIX-like operations over a schema/revision model; blobs, metadata, and path resolution remain authoritative here rather than in execution environments.

• packages/dofs/src/fs/filesystem.ts

• packages/dofs/src/schema/core.ts

• packages/dofs/src/storage.ts

The sync subsystem computes, transfers, applies, and coalesces changes between this store and remote projections, including blob and watermark handling.

• packages/dofs/src/sync/push.ts

• packages/dofs/src/sync/fetch.ts

• packages/dofs/src/sync/apply.ts

Runtime Backends

Three execution paths implement the runtime abstraction:

• Container: projects the workspace into a sandbox container with a real FUSE filesystem and Linux userland. packages/computer/src/backends/container/cloudflare-container.ts, packages/computer/src/backends/container/container-lifecycle.ts

• Isolate shell: runs just-bash in a Cloudflare Dynamic Worker and accesses Workspace directly over Workers RPC. packages/computer/src/backends/worker-shell/worker-shell.ts, packages/computer/src/backends/worker-shell/adapter.ts

• Isolate JavaScript: evaluates modules in fresh Dynamic Workers, supplying Workspace-backed filesystem support and curated modules/imports. packages/computer/src/backends/worker-javascript/worker-javascript.ts, packages/computer/src/backends/worker-javascript/module-graph.ts

Container Daemon and RPC Boundary

computerd runs inside the container as a Node daemon. It exposes HTTP/WebSocket RPC, mounts the remote filesystem through FUSE, and executes local processes against that mount. This creates the principal distributed boundary: container-side filesystem operations synchronize to the Durable Object store over Cap’n Web RPC.

• packages/computerd/src/cli/computerd.ts

• packages/computerd/src/fuse/vfs.ts

• packages/computerd/src/exec/runner.ts

@cloudflare/computer-rpc defines shared client/server and wire interfaces used across that boundary.

• packages/rpc/src/interface.ts

• packages/rpc/src/client.ts

• packages/rpc/src/server.ts

Integrated Services and Capability Surfaces

Computer exposes workspace-aware Git, artifacts, asset upload, mounts, and agent-oriented tools as higher-level capability surfaces. These sit above the authoritative filesystem and runtime selection rather than replacing either.

• packages/computer/src/git/index.ts

• packages/computer/src/artifacts/index.ts

• packages/computer/src/assets/index.ts

External infrastructure includes Cloudflare Durable Objects with SQLite, Workers RPC and Dynamic Workers, Cloudflare Containers, R2-backed mounts, Workers AI, and Cloudflare Artifacts. The container release image is assembled around a prebuilt Linux x64 daemon in packages/computer-computerd-linux-x64/Dockerfile.

Consumer Shapes

Runnable Workers under examples/ are integration entry points rather than core services: HTTP workspace demos start at examples/container/src/index.ts, examples/worker-shell/src/index.ts, and examples/worker-javascript/src/index.ts. The comparison application combines a browser UI with a Worker orchestrator for side-by-side container and isolate agent runs: examples/think-compare-runtimes/worker/index.ts.