Cloudflare gives each AI agent a computer, not a container
@cloudflare/computer runs agent shells on cheap isolates, hitting containers under 10% of the time — plus cross-language RPC, inbound gRPC and a billing API.
Copy markdown
One filesystem, three ways to run it
@cloudflare/computer hands every agent a SQLite-backed virtual filesystem on a Durable Object, then runs its shell in either a cheap Worker isolate (bash transpiled to JS) or a full Linux container mounted via FUSE. Cloudflare wants containers handling under 10% of agent work, so you pay isolate prices for most coding, file-editing and doc tasks. It's open-source (MIT) with AI-SDK tools — but explicitly flagged 'not for production' yet.
Python and JS Workers now call each other
Workers RPC now crosses languages: a JavaScript Worker can 'await rpc.add(42, 144)' straight into a Python Worker and back, with no schemas, no serialization, and near-zero overhead since the call never touches the network. int/float, bool, dict/list and even Request/Response map natively — so you can reach for a Python-only package from JS without writing a bridge.
Inbound gRPC and raw TCP land on Workers
A new connect(socket) handler lets Workers accept inbound TCP from Spectrum, and Containers can terminate full-duplex gRPC with automatic gRPC-to-gRPC-web translation across 330+ locations. Put your existing mobile or voice-AI gRPC backend behind Workers with no client changes. It's in private beta — sign up to get access.
A billing API your agent can actually read
The new Billable Usage API returns per-service cost and usage across Workers, R2, D1, Workers AI, Vectorize, Images and Stream from one endpoint — FOCUS-standard and refreshed daily. It's live free on every self-serve account, so an autonomous agent (or your finance dashboard) can watch spend with a single curl instead of dashboard screenshots.