Summary
Cloudflare introduced @cloudflare/ci, a CI/CD system built on Cloudflare Workflows that replaces YAML pipelines with TypeScript. Because pipelines are Workflows, they can self-heal and spawn AI agents to handle more complex tasks, and Cloudflare pitches running CI/CD for millions of repositories on its own platform.
What changed
On August 4, 2026 Cloudflare launched @cloudflare/ci, letting teams define CI/CD pipelines as TypeScript Cloudflare Workflows instead of YAML, pipelines that can self-heal and spawn agents and run at scale on Cloudflare's platform.
Why it matters
CI/CD is where agent-generated code gets validated and shipped, and expressing pipelines as code-first Workflows makes them programmable and agent-drivable rather than static config. It extends Cloudflare's Workers and Workflows platform into the build-and-deploy layer and targets platform builders who want to offer CI to their own users.
Evidence excerpt
A CI/CD pipeline is just a Workflow. But a Workflow can be so much more than a CI/CD pipeline.