Cloudflare Wants You to Rebuild GitHub for 10,000 Agents (for $25K)

Last updated: October 4, 2026 · 6-minute read

Here is the most interesting question in developer tooling right now, asked out loud by Cloudflare with money attached: what does the next GitHub look like when the users are agents? GitHub was built for a world where humans write code, organize it into repositories, and collaborate through branches, commits, issues and pull requests. The next generation of software is being built by a different kind of developer — agents, by the hundreds and thousands, working the same codebase simultaneously. Cloudflare thinks the platform layer for that world does not exist yet, and it has launched a competition to get it built on top of Artifacts, its versioned filesystem that speaks Git, now in open beta. Deadline: October 14, 2026. First place: $25,000 in Cloudflare credits and a slot at Cloudflare Connect in San Francisco.

The problem statement is a list of unanswered questions

Cloudflare's framing of the gap is the sharpest part of the announcement, and it deserves to be quoted as a checklist, because every item is an unsolved product problem: How do agents know what other agents are working on? What happens when they make conflicting changes? How do you review everything they produce? How do you track not just what changed, but why a change was made?

Read that list against what Git actually provides and the shape of the missing layer becomes visible. Git gives you history, but agent history is noise without intent — a thousand commits a day tell you nothing about which thousand decisions were load-bearing. Git gives you branches, but nothing about branch ownership: which agent holds this worktree, what task is it solving, when does its lease expire. Git gives you merge conflicts, but a conflict between two machine-generated patches is a different beast than a conflict between two humans — the resolution might be mechanical, or might require an arbiter that understands both tasks' intent. The primitives exist. The collaboration layer on top is what Cloudflare says is missing — and what it refuses to prescribe.

What Artifacts actually gives you to build with

Artifacts launched earlier this year as "a versioned filesystem that speaks Git" designed to scale to a repository per agent, per session, per task, per user — programmatically created and forked. The open beta ships with capabilities that map suspiciously well onto the problem statement:

Deploy from the repo. Artifacts repositories connect to Workers Builds — push to the production branch and Cloudflare builds and deploys the Worker; pushes to other branches create isolated, shareable Previews. For agents, that means every branch is automatically a running, testable environment. Review-as-deploy, without building the pipeline.

A Git API inside Workers. Through an Artifacts binding, a Worker can create and fork repos, inspect files and commits, and issue repo-scoped Git tokens. Cloudflare's own example is the agent-orchestration loop in ~10 lines: fork the project for a task, read its AGENTS.md for instructions, hand the agent a workspace with its own remote and token.

using repo = await env.ARTIFACTS.get(workspace.name); const instructions = await repo.readFile({ ref: defaultBranch, path: "AGENTS.md", });

Event subscriptions. Artifacts publishes events — repo created, forked, pushed, deleted, fetched — and a Worker can subscribe. The announcement's example wires cf.artifacts.repo.pushed into a review Workflow: every push spawns a code-review run with the repo, branch and commit attached. That is CI, review orchestration and agent coordination built on one primitive.

Jurisdiction and metrics. Namespaces can pin storage and processing to US or EU jurisdictions — the compliance checkbox agent platforms will need the day their enterprise customers ask. And per-repo metrics (operations, pulls, pushes, errors) landed in the dashboard, with queryable data for custom monitoring.

Pricing is operations-plus-storage, with billing beginning October 15, 2026 — the day after the competition closes, which tells you exactly how Cloudflare sequenced this. Artifacts requires the Workers Paid plan.

What the judges actually want

The brief is refreshingly specific about what will lose: "We aren't looking for GitHub as it exists today with agents added on top." At minimum, submissions must show multiple agents working on changes concurrently. Beyond that, Cloudflare invites teams to rethink repositories, branches, pull requests, worktrees, code review and merge conflicts — or to build new ways to preserve agent context, compare multiple changes side by side, and decide which one ships.

Submissions need three things: a 5-10 minute video demonstrating what was built and how it works, the source code under a permissive license (MIT, Apache or BSD), and instructions for running it. The top three teams get flown — up to two members each — to Cloudflare Connect to demo; the first-place team takes the $25,000 in credits plus invitations to the VIP speaker dinner.

If I were pitching this competition

Given ten days, the pitch I would build: the provenance-first review queue. Every push to an Artifacts repo spawns a review record that binds together the task brief, the agent's instructions file, the diff, the test run, and a machine-checkable claim about scope — then a Worker workflow scores the claim against the repo's own conventions and surfaces a one-screen verdict: what changed, why, what it proves, what remains unproven. Fork-per-task comes free from the Artifacts binding; the competing teams all get that. The differentiator is the verdict layer — because "multiple agents working concurrently" is the entry fee, and "a human can audit a thousand agent commits an hour" is the product nobody has shipped yet.

The second-order idea worth stealing for any entry: context as a repo artifact. Artifacts stores code and agent context side by side by design — the teams that treat the context (briefs, decisions, rejected approaches) as a first-class versioned object, not a README afterthought, will have the only demo where the "why" question from Cloudflare's problem statement gets answered on stage.

TL;DR

• Artifacts: Cloudflare's Git-speaking versioned filesystem, now open beta (Workers Paid).
• New: Workers Builds deploys from Artifacts repos, an in-Worker Git binding, push events, EU/US jurisdictions, metrics; billing starts Oct 15, 2026.
• Competition deadline Oct 14, 2026 — video, permissively-licensed source, run instructions; $25K credits plus Cloudflare Connect.
• The brief: multiple agents working concurrently; the winning layer will be review and provenance, not more commits.

My take: the review layer is the whole game

Anyone can make agents commit more code — that is the default trajectory of the universe we live in. The scarce, unbuildable-without-imitating-someone-else part is the layer that answers Cloudflare's fourth question: why did a change happen, and can a reviewer — human or machine — trust it? The teams that win this competition will be the ones that treat every agent commit as a claim with evidence attached: task provenance, the instructions it worked from, the tests it ran, the diffs it considered and rejected. Fork-per-task is table stakes — the Artifacts binding makes it a weekend project. The hard product is the arbiter: the thing that takes N agent-produced patches solving the same task and produces a decision a human can audit in 30 seconds.

That is also why this competition matters beyond the prize. The industry's agent tooling is converging on the same architecture from every direction — agent workflows that survived 90 days in production already behave like this informally, and Agent Deck is the same coordination problem at the single-developer scale. Whoever shapes the review layer for machine-generated code shapes the next decade of software quality. Cloudflare is not just running a hackathon — it is crowd-sourcing the design document for infrastructure it will probably end up productizing.

If you have ten days and an opinion about what code review should look like when none of the code was written by humans, the entry form is on Cloudflare's blog. The rest of this site's agent coverage — including where always-on agents like OpenAI's Dots are heading — lives in the blog.

---

Not affiliated with Cloudflare or GitHub. Sources: the Cloudflare blog announcement "We want you to build the next Git platform on Cloudflare" (Oct 1, 2026) and Cloudflare's Artifacts documentation as referenced there.