Cloudflare Artifacts targets agent workspaces

Cloudflare is aiming at the real bottleneck in agentic software: state, isolation, and repo throughput, not model quality. If agents are going to run in parallel at scale, a Git-native storage layer is a sensible place to build.

• –One repo per agent, session, or sandbox reduces merge-conflict chaos and makes parallel work easier to reason about
• –REST and Workers APIs let serverless code create repos and credentials without forcing every workflow through a Git client
• –ArtifactFS is the practical wedge here: faster large-repo hydration means agents spend less time waiting and more time working
• –Native git-notes for prompts and attribution is a clean way to attach agent metadata without mutating content
• –The launch feels more infra than app: Cloudflare is selling the substrate for agent workloads, not another coding assistant