Cloudflare moved Artifacts into open beta on October 1, 2026, offering Git repositories as programmable infrastructure for applications and coding agents. The release adds Workers integration and deployment workflows; it is a foundation on which developers can build a Git platform, rather than a complete hosted review product. The announcement sets out that scope and says billing starts October 15.
Repositories become part of application logic
Artifacts can connect repository pushes to Workers Builds, with production-branch deployments and previews for other branches. Its event subscriptions also let applications react to repository activity. That opens a straightforward pattern: give an agent an isolated repository, collect its commits, then trigger review without granting it access to the production branch.
The isolation must be designed into the workflow. A fork separates file changes, but it does not by itself prevent an agent from accessing secrets supplied by its runtime or deploying through another tool. Review all of the capabilities available to the agent, not just the Git remote.
Token scope is a practical security boundary
The Workers binding documentation describes repository operations and the creation of read or write tokens with a lifetime. Those primitives allow an application to issue a narrower credential for a specific task instead of sharing its own broad administrative access.
A review-only agent should receive read access. A coding task may need write access to its workspace, with a lifetime aligned to the task rather than an indefinitely reusable credential. Avoid putting issued tokens in task transcripts or build logs. Treat repository content as untrusted input when an agent reads instructions from it; a committed file should not be allowed to redefine application authorization.
Build review and recovery before broad automation
Repository events are useful triggers, but a trigger is not a complete job-management system. Associate a review with the commit it examined so that a later push cannot inherit an earlier approval. Make repeated delivery safe and show failed review jobs to the owner instead of silently dropping them.
Before adopting the beta, test import, fork, push, preview and recovery with a representative project. Estimate repository-operation and storage usage before October 15. The product is especially relevant when Git is embedded inside an agent platform; teams primarily seeking mature pull-request collaboration should compare that requirement separately from the storage primitive.