Cloudflare competition asks developers to build agent-native Git hosting

Cloudflare is running a competition that asks developers to design the Git platform of the agentic era — code hosting built for AI agents rather than human programmers — on top of its Workers runtime and Artifacts storage service. Alongside the call, the company announced a batch of new Artifacts capabilities and a date for billing to begin.

The premise: hosting for machine developers

According to the Cloudflare blog, today's code-hosting conventions — repositories, branches, issues and pull requests — were designed around people writing and reviewing code. Cloudflare's argument is that agents already produce a large share of code, handling bug fixes, features, tests, reviews and dependency maintenance, and that the foundation shifts once hundreds or thousands of them work on the same codebase simultaneously. The open questions it raises include how agents learn what others are doing, how conflicting machine-made changes get reconciled, how output is reviewed at that volume, and how the reasoning behind a change — not just the diff — gets recorded.

Entrants are expected to go beyond today's GitHub with agents layered on top. The stated minimum is multiple agents working on changes concurrently; from there, Cloudflare suggests rethinking branches, pull requests, worktrees, code review and merge conflicts, or inventing ways to preserve agent context, compare several candidate changes side by side and decide which one ships.

What Artifacts now provides

Artifacts, which Cloudflare launched earlier this year and which is now in open beta, is a versioned storage service that implements Git and is designed to scale to millions of repositories. Repositories can be created and forked programmatically, code and agent context get versioned storage, and agents can use the Git operations they already know.

The new capabilities announced with the competition:

• Workers Builds integration. An Artifacts repository can be connected to a Worker, so pushes to the production branch build and deploy the updated Worker, while pushes to other branches spin up or refresh Workers Previews for isolated testing.
• An Artifacts binding for Workers. Code running on Workers can create or fork repositories, inspect files and commits, and issue repository-scoped Git tokens — for example, forking a project for each incoming task and reading its AGENTS.md instructions.
• Event subscriptions. Artifacts emits events whenever a repository is created, imported, forked, deleted, pushed to, cloned or fetched, letting a Worker trigger CI, start a review agent or deploy on every change.
• Data jurisdiction. Namespaces can be pinned to US or EU storage and processing, and repositories created inside them inherit the restriction.
• Metrics. Per-repository totals for operations, pulls, pushes, errors and error rate are visible in the Cloudflare dashboard and can be queried directly for custom dashboards and monitoring.

Cloudflare says early adopters are already using Artifacts to store projects built on vibe-coding platforms, persist code and context from agent sessions, and spin up isolated repositories so multiple agents can start from the same point and merge results later.

Competition details

Submissions are open until October 14, 2026. Entries need a five-to-ten-minute video demonstrating the build, a link to source code released under a permissive license (MIT, Apache or BSD), and instructions for running the project.

Cloudflare will select three winning teams and fly up to two members of each to San Francisco to demonstrate their work at Cloudflare Connect. The first-place team also receives $25,000 in Cloudflare credits and an invitation to the event's VIP speaker dinner.

Artifacts itself is available in open beta to customers on the Workers Paid plan. Billing, based on repository operations and the amount of data stored, begins October 15, 2026.

Why it matters

The competition is a wager that code collaboration gets rebuilt around machines. Cloudflare is deliberately not building the coordination and review layer itself; it is supplying storage, Git primitives and event-driven compute, then letting others experiment with what replaces the pull request. For participants, the prizes are modest, but the timing — Artifacts billing starts the day after the submission deadline — suggests the real goal is seeding an ecosystem on Workers before agent-native tooling consolidates elsewhere. If agentic coding keeps growing, whatever abstractions win here sketch the shape of GitHub's successor: a system where capturing why an agent changed something matters as much as reviewing what it changed.