5 articles
On August 5 Cloudflare published the Agent Access Model: a reference architecture where credentials are short-lived and task-scoped, enforcement lives in the harness and network instead of the prompt, and a Trust Ratchet only narrows an agent's capabilities. The cleanest spec yet for least privilege at agent speed.
On August 5 Cloudflare open sourced Cloudflare OS, the agent workspace it has run internally since May: capability-based Gatekeepers instead of ambient MCP access, apps as private per-user instances, and approvals that simulate outcomes so agents never stall. A concrete blueprint for the company-wide agent platform.
On August 4 Cloudflare launched the Agent Development Lifecycle: agent traces with session replay, @cloudflare/ci for CI/CD as Workflows, and local OpenTelemetry. A software factory is no longer just an idea, it is a platform product.
Cloudflare's new CI SDK runs pipelines as Workflows: TypeScript instead of YAML, cached sandbox steps, artifact-push triggers, and a healing agent that fixes failed builds. Here is how it works and what it means for platforms.
Day three of Agents Week brought Cloudflare Wallets: Account Wallets for humans and Virtual Wallets for agents, x402 stablecoin micropayments for APIs and content, and human-readable agent identity at handles like research.example.cloudflare.pay.
Showing 4 of 4 articles
New tutorials, open-source projects, and deep dives on coding agents - delivered weekly.
Explore 834 topics
Browse All Topics