excited to announce that Cloudflare Artifacts is now in open beta! with Artifacts, you can give every application and agent its own repo that you can manage programmatically plus you can use it to store and deploy your Workers code (and ofc it integrates with Workers Previews)

created by one of the most goated teams at @Cloudflare huge shoutout to @zebassembly @dillon_mulroy @ivarvong @mdhruvill @leostera @ericclemmons @southpolesteve check it out:

@Cloudflare interesting... 👀

@Cloudflare github should be getting nervous right about now

@Cloudflare a repo per agent means one agent's bad afternoon reverts without touching the others.

@Cloudflare Oh awesome! Congrats!

@Cloudflare a repo per agent is a nice primitive. git history ends up being the audit log agents never had

@Cloudflare oh damn

I’d keep the rejected attempts around too. Otherwise the next agent gets to discover the same dead end all over again.

@Cloudflare congrats!

@Cloudflare Per-agent repos give each agent its own history, which makes rolling back one bad run trivial. How does an agent's branch get merged into a human-owned repo?

@Cloudflare This is the right primitive. What breaks long-running agents usually isn't the model, it's state: no memory of what they changed, no way to roll back. A real repo per agent gives them both. Version control turns out to be agent infrastructure, not just dev tooling.

@Cloudflare Love cloudflare

@eastdakota @Cloudflare 🐐

Artifacts giving every app/agent a programmatic repo + Workers preview is the right shape for ship loops.We're mirroring that discipline for onchain web works: import → preview → human confirm → publish/verify (BSC / X Layer / Base), with WebMCP so the agent prepares but doesn't self-approve.

@Cloudflare Love what Cloudflare is doing lately!

This approach is way cooler than it might seem at first. If I understand it correctly, it lets you work with any dataset that can be stored in Git, with versioning and the same workflows you already use for code. And you don’t have to deal with Git LFS. Git for everything. Very cool.

@Cloudflare Agentic layer @IndyDevDan

@Cloudflare The repo-scoped tokens are the bit I like. Fixing one app shouldn't give an agent push access to everything else in the account.

@Cloudflare WOW

@Cloudflare cooool 🔥

@Cloudflare hi! can one from EU attend the competition?

A preview URL per task is useful. I'd put the exact commit SHA beside it and retire the preview when the task closes. Otherwise reviewers can end up approving a screen that no longer matches the change being merged.

@dillon_mulroy @Cloudflare ooooh this looks incredibly powerful CoW has come a loooong way 💪

@Cloudflare Damn your guys’ announcements is at the same pace as OpenAI and Anthropic!

@Cloudflare wow can't wait to try this!

@Cloudflare having separate repos for each application can simplify management and deployment