--- title: Artifacts Changelog image: https://edgetunnel-b2h.pages.dev/cf-twitter-card.png --- > Documentation Index > Fetch the complete documentation index at: https://edgetunnel-b2h.pages.dev/changelog/llms.txt > Use this file to discover all available pages before exploring further. [Skip to content](#%5Ftop) # Changelog New updates and improvements at Cloudflare. [ Subscribe to RSS ](https://edgetunnel-b2h.pages.dev/changelog/rss/index.xml) [ View RSS feeds ](https://edgetunnel-b2h.pages.dev/fundamentals/new-features/available-rss-feeds/) Artifacts ![hero image](https://edgetunnel-b2h.pages.dev/_astro/hero.CVYJHPAd_26AMqX.svg) Jun 17, 2026 1. ### [Manage Artifacts from the Cloudflare dashboard](https://edgetunnel-b2h.pages.dev/changelog/post/2026-06-17-dashboard-management/) [ Artifacts ](https://edgetunnel-b2h.pages.dev/artifacts/) You can now configure [Artifacts](https://edgetunnel-b2h.pages.dev/artifacts/concepts/how-artifacts-works/) namespaces, repos, and tokens directly from the Cloudflare dashboard. Artifacts is Git-compatible storage that lets you store repos on Cloudflare and interact with them using standard Git workflows. You can view and create [namespaces](https://edgetunnel-b2h.pages.dev/artifacts/concepts/namespaces/#use-namespaces-as-containers), which are top-level containers for repos: ![Artifacts namespaces dashboard showing namespace search and create namespace controls](https://edgetunnel-b2h.pages.dev/_astro/dashboard-namespaces.0BJelWZh_Z1uJ1iD.webp) You can view, create, fork, and search repos within a namespace: ![Artifacts repositories dashboard showing repo source, access, and created columns](https://edgetunnel-b2h.pages.dev/_astro/dashboard-repositories.M9P9JUL__Agf9h.webp) You can open a repo to view its files and copy its Git remote URL. ![Artifacts repository overview showing files, commits, token management, and quick actions](https://edgetunnel-b2h.pages.dev/_astro/dashboard-repo-overview.CSHxrCW2_81obq.webp) You can also provision tokens directly from the dashboard to scope Git access to a single repo, with read tokens for clone, fetch, and pull workflows, or write tokens when a client needs to push changes. To get started, go to the [Cloudflare dashboard ↗](https://dash.cloudflare.com/) and select **Storage & databases** \> **Artifacts**. If you are enrolled in the Artifacts beta, you can use the dashboard to set up Artifacts. If you would like to join the beta, complete the [request form ↗](https://forms.gle/DwBoPRa3CWQ8ajFp7). May 19, 2026 1. ### [Event subscriptions for Artifacts lifecycle events](https://edgetunnel-b2h.pages.dev/changelog/post/2026-05-19-event-subscriptions/) [ Artifacts ](https://edgetunnel-b2h.pages.dev/artifacts/)[ Queues ](https://edgetunnel-b2h.pages.dev/queues/) You can now receive [event notifications](https://edgetunnel-b2h.pages.dev/queues/event-subscriptions/) for [Artifacts](https://edgetunnel-b2h.pages.dev/artifacts/) repository changes and consume them from a Worker to build commit-driven automation. This allows you to: * Run custom workflows when a repository is created or imported * Kick off a build and deploy a change when an agent pushes to a repo * Trigger a review agent on every push Available events include: * **Account-level events** (`artifacts` source) — `repo.created`, `repo.deleted`, `repo.forked`, `repo.imported` * **Repository-level events** (`artifacts.repo` source) — `pushed`, `cloned`, `fetched` To learn more, refer to [Artifacts documentation](https://edgetunnel-b2h.pages.dev/artifacts/guides/event-subscriptions/). May 18, 2026 1. ### [Manage Artifacts namespaces and repos with Wrangler CLI](https://edgetunnel-b2h.pages.dev/changelog/post/2026-05-18-wrangler-support/) [ Artifacts ](https://edgetunnel-b2h.pages.dev/artifacts/) You can now manage [Artifacts](https://edgetunnel-b2h.pages.dev/artifacts/) namespaces, repos, and repo-scoped tokens directly from Wrangler CLI. Available commands: * `wrangler artifacts namespaces list` — List Artifacts namespaces in your account. * `wrangler artifacts namespaces get` — Get metadata for a namespace. * `wrangler artifacts repos create` — Create a repo in a namespace. * `wrangler artifacts repos list` — List repos in a namespace. * `wrangler artifacts repos get` — Get metadata for a repo. * `wrangler artifacts repos delete` — Delete a repo. * `wrangler artifacts repos issue-token` — Issue a repo-scoped token for Git access. To get started, refer to the [Wrangler Artifacts commands documentation](https://edgetunnel-b2h.pages.dev/workers/wrangler/commands/artifacts/). Apr 16, 2026 1. ### [Artifacts now in beta: versioned filesystem with Git access](https://edgetunnel-b2h.pages.dev/changelog/post/2026-04-16-artifacts-now-in-beta/) [ Artifacts ](https://edgetunnel-b2h.pages.dev/artifacts/) [Artifacts](https://edgetunnel-b2h.pages.dev/artifacts/) is now in private beta. Artifacts is Git-compatible storage built for scale: create tens of millions of repos, fork from any remote, and hand off a URL to any Git client. It provides a versioned filesystem for storing and exchanging file trees across Workers, the REST API, and any Git client, running locally or within an agent. You can [read the announcement blog ↗](https://blog.cloudflare.com/artifacts-git-for-agents-beta/) to learn more about what Artifacts does, how it works, and how to create repositories for your agents to use. Artifacts has three API surfaces: * Workers bindings (for creating and managing repositories) * REST API (for creating and managing repos from any other compute platform) * Git protocol (for interacting with repos) As an example: you can use the Workers binding to create a repo and read back its remote URL: **TypeScript** ```ts # Create a thousand, a million or ten million repos: one for every agent, for every upstream branch, or every user. const created = await env.PROD_ARTIFACTS.create("agent-007"); const remote = (await created.repo.info())?.remote; ``` Or, use the REST API to create a repo inside a namespace from your agent(s) running on any platform: ```bash curl --request POST "https://artifacts.cloudflare.net/v1/api/namespaces/some-namespace/repos" --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" --header "Content-Type: application/json" --data '{"name":"agent-007"}' ``` Any Git client that speaks smart HTTP can use the returned remote URL: ```bash # Agents know git. # Every repository can act as a git repo, allowing agents to interact with Artifacts the way they know best: using the git CLI. git clone https://x:${REPO_TOKEN}@artifacts.cloudflare.net/some-namespace/agent-007.git ``` To learn more, refer to [Get started](https://edgetunnel-b2h.pages.dev/artifacts/get-started/), [Workers binding](https://edgetunnel-b2h.pages.dev/artifacts/api/workers-binding/), and [Git protocol](https://edgetunnel-b2h.pages.dev/artifacts/api/git-protocol/). ```json {"@context":"https://schema.org","@type":"BlogPosting","@id":"https://edgetunnel-b2h.pages.dev/changelog/product/artifacts/#page","headline":"Artifacts Changelog | Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/changelog/product/artifacts/","inLanguage":"en","image":"https://edgetunnel-b2h.pages.dev/cf-twitter-card.png","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://edgetunnel-b2h.pages.dev/#website","name":"Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/"}} ```