Cloudflare Artifacts can now be developed and tested locally
Artifacts bindings default to a local Git simulator during development, so you can test Workflow triggers without touching production data, though build-on-push still needs a real deploy.
Cloudflare shipped local development support for Artifacts on 16 November. Artifacts, in open beta since October, gives Workers a versioned, Git-backed filesystem: you can create repos, import existing Git repositories over HTTPS, issue repo tokens, and now clone and push with a local git client before anything touches Cloudflare’s network.
The useful part is that local repos fire the same events as production, repo created, imported, forked or deleted, token created or revoked, so a Workflow that reacts to those events can be tested on your machine first. It needs Git 2.32 or later on your PATH and a recent Wrangler. Cloudflare also flipped the default: an Artifacts binding with no remote setting used to hit your deployed repo, and now defaults to the local simulator instead.
Why it matters: that default flip is the kind of thing that bites people quietly. If you built an Artifacts-backed Workflow before this shipped, your next wrangler dev session reads from a local simulator rather than the deployed repo, unless you explicitly set remote: true on the binding.
The caveat: push, clone and fetch events don’t publish locally yet, so a Workflow set up to build and deploy on push still won’t fire until you actually deploy.