GitHub was built for a earth anywhere humans compose code, arrange it into repositories, and collaborate through branches, commits, issues, and drag requests.
But the next generation of application is going to be built alternatively since it is going to be built by a distinct benevolent of developer: agents.
Agents are already penning additional code than always before — they’re fixing bugs, construction features, penning tests, reviewing changes, updating dependencies, and doing the regular care required to keep an use running.
So in this new earth anywhere you have hundreds, or equal thousands, of agents operating on the identical codebase at the identical time, what does the basis appearance like?
How do agents cognize what another agents are operating on? What happens whenever they create conflicting changes? How do you assessment everything they produce? How do you keep track of not fair what changed, but why a alter was made?
And so the burning inquiry is: What does the next GitHub appearance like?
We desire you to assistance us answer it, by construction it out.
Earlier this year, we launched Artifacts, a versioned filesystem that speaks Git and can measure 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 retention for code and delegate context, and the Git operations agents already cognize how to use.
With that basis in place, you can concentration on the tier complete it: how agents coordinate their work, how changes are reviewed and merged, and what the developer cognition should appearance akin whenever hundreds or thousands of agents are operating on the identical codebase.
That is the tier we desire you to build.
Now that Artifacts is in open beta, we’re holding a competition to see who can build the next Git phase on Cloudflare using Workers and Artifacts.
Artifacts is in open beta. Here’s why you should build on it
When we launched Artifacts, our goal was to create it imaginable to create a repository for all agent, session, task, or person — and to do that at the measure agents require.
Since then, we’ve seen developers use Artifacts in a range of ways: Vibe-coding platforms are using it to shop the projects their users create. Developers are using it to persist the code and environment from delegate sessions. Others are creating secluded repositories, so multiple agents can safely activity from the identical starting item and difference or merge the results later.
Here are several new capabilities we’ve added since the first launch.
Deploy Artifacts repos to Workers
You can now nexus an Artifacts repository to a Worker through Workers Builds. When you or an delegate pushes code to the Artifacts repository, Cloudflare volition build the project and, for the manufacturing branch, deploy the updated Worker. Pushes to another branches automatically create or update Workers Previews, giving you an isolated, shareable type of your Worker anywhere you can test changes before they go live.
You can nexus an existing Worker to an Artifacts repository or commencement a new project and automatically shop it in Artifacts.
Manage Artifacts immediately from Workers
You can engage alongside Artifacts repositories immediately from a Worker using an Artifacts binding to create or fork repos, inspect records and commits, and matter repo-scoped Git tokens. This makes your Git workflow programmable. When a new project arrives, a Worker can fork the project for an agent, peruse the records it needs for context, and provision it a repository to activity in. When the delegate pushes a change, your automation can inspect the outcome and commencement 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 delegate project and peruse its AGENTS.md for instructions:
using project = await env.ARTIFACTS.get("my-project"); const { defaultBranch } = await project.info(); const workspace = await project.fork(`task-${crypto.randomUUID()}`); using repo = await env.ARTIFACTS.get(workspace.name); const instructions = await repo.readFile({ ref: defaultBranch, path: "AGENTS.md", }); const agentTask = { remote: workspace.remote, token: workspace.token, instructions: instructions ? await instructions.text() : null, };
React to all alter alongside event subscriptions
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, boot off a code assessment agent, or deploy a change.
For example, you can subscribe to Artifacts shove events and have a Worker commencement a code assessment workflow for all push. The Worker passes the repository, branch, and new commit to the Workflow, giving a assessment delegate the environment it needs to inspect the change:
export default { async queue(batch, env) { for (const message of batch.messages) { const event = message.body; if (event.type !== "cf.artifacts.repo.pushed") continue; await env.REVIEW_WORKFLOW.create({ params: { namespace: event.source.namespace, repo: event.source.repoName, ref: event.payload.ref, commit: event.payload.after, }, }); } }, };
Data jurisdiction for Artifacts repos
You can now choose anywhere Artifacts stores and processes your repository data. Set a U.S. or EU jurisdiction whenever you create a namespace, and all repository created in that namespace volition automatically prosecute the identical restriction.
curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/artifacts/namespaces" \ -H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \ --json '{"namespace":"my-eu-namespace","jurisdiction":"eu"}'
View Artifacts metrics
You can now see metrics for your Artifacts repositories in the Cloudflare dashboard. For all repository, you can now see total operations, pulls, pushes, errors, and error rate, assisting you comprehend how the repository is being used and place failures. You can additionally query Artifacts metrics directly to build your own dashboards or monitoring.
Pricing
Artifacts pricing is according to repository operations and the amount of data stored. We volition commencement billing for Artifacts use on October 15, 2026.
Competition: Build the next Git phase on Cloudflare
We desire you to build your imagination for the Git phase of the agentic era using Cloudflare Workers and Artifacts.
You could rethink repositories, branches, drag requests, worktrees, code review, and merge conflicts — or build new ways to maintain delegate context, difference multiple changes at the identical time, and decide which one should ship.
We aren’t looking for GitHub as it exists today alongside agents added on top. At a minimum, we desire to see multiple agents operating on changes concurrently. Beyond that, we desire you to get imaginative — what you think comes next.
How to enter
Submit:
- A 5-10 infinitesimal video demonstrating what you built, what it enables agents and developers to do, and how it works
- A nexus to the origin code, which must be provided under a permissive open origin licence (MIT, Apache, BSD)
- Instructions for operating or trying the project
Deadline
Submissions are open until October 14, 2026.
Why should you participate?
We’ll choose the top three projects and fly up to two members from all squad to San Francisco to act Cloudflare Connect and display what they built.
The first-place squad volition additionally obtain $25,000 in Cloudflare credits, alongside alongside invitations to the VIP speaker meal on Monday night at Connect.
Get started
Artifacts is available in open beta to customers on the Workers Paid plan.
Get started alongside your coding agent: copy the immediate below to set up your archetypal Artifacts repository and commencement pushing code to it.
You can perspective or create the Artifacts repositories in the dashboard or if you’re looking to study more, inspect out the documentation.
