Cloudflare Launches Competition to Build Agent-Centric Git Platforms on Artifacts and Workers

Cloudflare Launches Competition to Build Agent-Centric Git Platforms on Artifacts and Workers Cloudflare has introduced new capabilities for Artifacts—its Git-compatible versioned filesystem in open beta—and launched a competition challenging developers to build a next-generation Git platform designed specifically for concurrent AI agents. Artifacts is available in open beta for Workers Paid customers, providing programmable primitives and Git storage scaled for AI agents. New features include Workers Builds CI/CD integration, Worker bindings for programmable repository management, event triggers, US/EU data localization, and repository metrics. The competition accepts submissions until October 14, 2026, awarding trips to Cloudflare Connect for three teams and $25,000 in credits to the winner. Artifacts Upgrades and Programmable Capabilities Cloudflare added several integrations to Artifacts, including Workers Builds, which builds and deploys production branches while creating Workers Previews for alternative branches. Developers can also use Worker bindings to programmatically fork repos, read files, and issue Git tokens. Additionally, Artifacts now publishes repository lifecycle events for automated CI/CD and review triggers, supports US and EU data localization namespaces, and provides dashboard metrics to track repository operations and errors. Competition Goals, Prizes, and Billing Schedule The competition asks participants to rethink core Git concepts like pull requests, branches, and conflict resolution for environments where multiple agents collaborate concurrently. Submissions remain open through October 14, 2026. Up to two members from the top three teams will be flown to San Francisco to present at Cloudflare Connect, with the first-place team receiving $25,000 in Cloudflare credits and a VIP speaker dinner invitation. Billing for Artifacts storage and operations will commence on October 15, 2026.

Cloudflare 举办 Git 平台构建竞赛，基于 Artifacts 探索 Agent 时代的开发协作 Cloudflare 宣布为其专为 AI Agent 设计的 Git 版本控制文件系统 Artifacts 启动公开测试，并举办开发者竞赛，鼓励开发者结合 Workers 与 Artifacts 打造适应成百上千 Agent 并发协作的新一代 Git 平台。 Cloudflare 认为未来的软件将主要由 Agent 构建，传统的 GitHub 工作流难以应对大规模 Agent 并发开发、审查与冲突管理。 Artifacts 现已开启公测，新增 Workers Builds 集成、Workers 绑定接口、事件订阅、数据本地化存储与仪表盘指标监控等功能。 Cloudflare 举办竞赛征集下一代 Git 平台，提交截止至 2026 年 10 月 14 日，获胜团队将获得旧金山大会行程与最高 25,000 美元抵扣金。 Artifacts 面向 Workers 付费计划客户开放公测，按操作次数和存储量计费，并将于 2026 年 10 月 15 日正式开始计费。 Agent 时代的 Git 基础与 Artifacts 现有 GitHub 模式是为人类开发者协作而设计的，面对成百上千个 Agent 同时在同一代码库中修复漏洞、开发功能与更新依赖的场景，代码协作、上下文追踪和冲突解决需要新的底层基础。Cloudflare 推出兼容 Git 协议且支持大规模扩展的版本控制文件系统 Artifacts，旨在让程序能够自动创建、复刻仓库，并存储代码及 Agent 上下文。 Artifacts 新增功能与可编程特性 Artifacts 引入了多项新能力：支持通过 Workers Builds 连接仓库实现自动构建与预览；开发者可通过 Workers 绑定直接在代码中复刻仓库、读取文件及签发访问令牌；支持订阅推送、分支变动等仓库事件来触发 CI 或代码审查工作流；提供美欧数据辖区设置以满足本地化合规，并支持在控制台查看与查询操作指标。 下一代 Git 平台竞赛与公测安排 Cloudflare 正式发起竞赛，要求参赛者基于 Workers 与 Artifacts 重构代码协作流程，实现真正的多 Agent 并发开发。竞赛提交截止时间为 2026 年 10 月 14 日，前三名团队成员将受邀前往旧金山参加 Cloudflare Connect，冠军团队还可获 25,000 美元 Cloudflare 抵扣额度。Artifacts 现对 Workers 付费用户开放，将于 2026 年 10 月 15 日按操作和存储开始计费。

GitHub was built for a world where humans write code, organize it into repositories, and collaborate through branches, commits, issues, and pull requests. But the next generation of software is going to be built differently because it is going to be built by a different kind of developer: agents. Agents are already writing more code than ever before — they’re fixing bugs, building features, writing tests, reviewing changes, updating dependencies, and doing the routine maintenance required to keep an application running. So in this new world where you have hundreds, or even thousands, of agents working on the same codebase at the same time, what does the foundation look like? 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 keep track of not just what changed, but *why* a change was made? And so the burning question is: **What does the next GitHub look like?** We want you to help us answer it, by building it out. Earlier this year, we launched [Artifacts](https://blog.cloudflare.com/artifacts-git-for-agents-beta/), a versioned filesystem that speaks Git and can scale to millions of repositories. From the start, we designed Artifacts as a set of programmable primitives that developers could use to build their own products, workflows, and abstractions. Artifacts provides the foundation: repositories that can be created and forked programmatically, versioned storage for code and agent context, and the Git operations agents already know how to use. With that foundation in place, you can focus on the layer above it: how agents coordinate their work, how changes are reviewed and merged, and what the developer experience should look like when hundreds or thousands of agents are working on the same codebase. That is the layer we want you to build. Now that Artifacts is in open beta, [we’re holding a competition](http://cloudflare.com/git-competition) to see who can build the next Git platform on Cloudflare using Workers and Artifacts. When we launched Artifacts, our goal was to make it possible to create a repository for every agent, session, task, or user — and to do that at the scale agents require. Since then, we’ve seen developers use Artifacts in a range of ways: Vibe-coding platforms are using it to store the projects their users create. Developers are using it to persist the code and context from agent sessions. Others are creating isolated repositories, so multiple agents can safely work from the same starting point and compare or merge the results later. Here are some new capabilities we’ve added since the initial launch. You can now connect an Artifacts repository to a Worker through [Workers Builds](https://developers.cloudflare.com/workers/ci-cd/builds/git-integration/artifacts-integration/). When you or an agent pushes code to the Artifacts repository, Cloudflare will build the project and, for the production branch, deploy the updated Worker. Pushes to other branches automatically create or update [Workers Previews](https://developers.cloudflare.com/workers/previews/), giving you an isolated, shareable version of your Worker where you can test changes before they go live. You can connect an existing Worker to an Artifacts repository or start a new project and automatically store it in Artifacts. You can interact with Artifacts repositories directly from a Worker using an [Artifacts binding](https://developers.cloudflare.com/artifacts/api/workers-binding/) to create or fork repos, inspect files and commits, and issue repo-scoped Git tokens. This makes your Git workflow programmable. When a new task arrives, a Worker can fork the project for an agent, read the files it needs for context, and give it a repository to work in. When the agent pushes a change, your automation can inspect the result and start a review. You define those steps in code to fit how your agents work. For example, here’s how to fork a project for a new agent task and read its `AGENTS.md` for instructions: Artifacts publishes events whenever a repository is created, imported, forked, deleted, pushed to, cloned, or fetched. You can subscribe to these events to decide what happens next: run CI, kick off a code review agent, or deploy a change. For example, you can subscribe to Artifacts push events and have a Worker start a code review workflow for each push. The Worker passes the repository, branch, and new commit to the Workflow, giving a review agent the context it needs to inspect the change: You can now [choose where Artifacts stores and processes](https://developers.cloudflare.com/artifacts/guides/data-localization/) your repository data. Set a U.S. or EU jurisdiction when you create a namespace, and every repository created in that namespace will automatically follow the same restriction. You can now see metrics for your Artifacts repositories in the Cloudflare dashboard. For each repository, you can now see total operations, pulls, pushes, errors, and error rate, helping you understand how the repository is being used and spot failures. You can also query [Artifacts metrics](https://developers.cloudflare.com/artifacts/observability/metrics/) directly to build your own dashboards or monitoring. Artifacts pricing is based on repository operations and the amount of data stored. We will begin billing for Artifacts usage on October 15, 2026. We want you to build your vision for the Git platform of the agentic era using Cloudflare Workers and Artifacts. You could rethink repositories, branches, pull requests, worktrees, code review, and merge conflicts — or build new ways to preserve agent context, compare multiple changes at the same time, and decide which one should ship. We aren’t looking for GitHub as it exists today with agents added on top. At a minimum, we want to see multiple agents working on changes concurrently. Beyond that, we want you to get creative — what you think comes next. Submit: [Submissions](http://cloudflare.com/git-competition) are open until October 14, 2026. We’ll select the top three projects and fly up to two members from each team to San Francisco to attend [Cloudflare Connect](https://www.cloudflare.com/connect/) and show what they built. The first-place team will also receive $25,000 in Cloudflare credits, along with invitations to the VIP speaker dinner on Monday night at Connect. Artifacts is available in open beta to customers on the Workers Paid plan. Get started with your coding agent: copy the prompt below to set up your first Artifacts repository and start pushing code to it. `Set me up with Cloudflare Artifacts so I can start pushing code to my first repository. Read https://developers.cloudflare.com/artifacts/llms.txt and https://developers.cloudflare.com/cf/llms.txt for current instructions. Use the Cloudflare cf CLI, installing it if needed. Help me authenticate, confirm my account and namespace, and verify Artifacts access. Create a new TypeScript Worker project with an ARTIFACTS binding and use it locally to create a repository on Cloudflare. Push an initial README commit and clone the repository separately to verify it works. Give me the repository's Git remote and instructions for pushing my own code. Keep credentials out of source control, Git configuration, remote URLs, and logs. Do not deploy or change billing settings. Stop the local server afterward. If anything fails, explain the blocker rather than claiming setup is complete.` You can view or create the Artifacts repositories in the [dashboard](https://dash.cloudflare.com/?to=/:account/workers/artifacts) or if you’re looking to learn more, check out the [documentation](https://developers.cloudflare.com/artifacts/).