workers: fix code example (#29799)

* [Artifacts] add docs scaffold

* [Artifacts] add get-started guides

* [Artifacts] add API references and pricing

* [Artifacts] add CODEOWNERS entry

* [Artifacts] fix pricing copy

* [Artifacts] expand beta changelog entry

* [Artifacts] align binding and git docs

* [Artifacts] correct REST and git endpoints

* [Artifacts] fix workers remote example

* [Artifacts] clarify import URL behavior

* [Artifacts] remove authenticated remotes page

* [Artifacts] expand metrics and limits docs

* [Artifacts] expand git and platform docs

* [Artifacts] clarify Git protocol docs

* [Artifacts] refresh ArtifactFS and examples

* [Artifacts] update pricing and limits docs

* [Artifacts] flesh out Sandbox SDK example

* [Artifacts] align docs to updated schema

* [Artifacts] clarify Sandbox SDK intro

* [Artifacts] trim Sandbox SDK example

* [Artifacts] strengthen overview

* [Artifacts] fix binding docs

* update

* [Artifacts] align docs with current runtime

* [Artifacts] tighten docs examples

* [Artifacts] clarify REST API auth

* [Artifacts] improve get started guides

* [Artifacts] address review nits

* [Artifacts] add repo naming and git notes guidance

* [Artifacts] reframe concepts docs

* [Artifacts] add guides and ArtifactFS docs

* [Artifacts] finalize docs updates

Author: elithrar

.github/CODEOWNERS

@@ -105,6 +105,7 @@ package.json @cloudflare/content-engineering
 
 # Developer Platform
 
+/src/content/docs/artifacts/ @elithrar @dmmulroy @mattzcarey @whoiskatrin @cloudflare/pcx-technical-writing @cloudflare/product-owners
 /src/content/docs/containers/ @mikenomitch @th0m @cloudflare/pcx-technical-writing @cloudflare/product-owners @cloudflare/cloudchamber
 /src/content/partials/containers/ @mikenomitch @th0m @cloudflare/pcx-technical-writing @cloudflare/product-owners @cloudflare/cloudchamber
 /src/content/docs/d1/ @elithrar @rozenmd @vy-ton @joshthoward @oxyjun @harshil1712 @cloudflare/pcx-technical-writing @cloudflare/product-owners

src/assets/images/artifacts/artifacts_diagram_architecture.png

@@ -0,0 +1,32 @@
+---
+title: "Artifacts now in beta: versioned filesystem with Git access"
+description: Artifacts is now available in beta as a versioned filesystem for Workers, APIs, and Git-compatible workflows.
+products:
+  - artifacts
+date: 2026-04-16
+---
+
+[Artifacts](/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 it works.
+
+You can use the Workers binding to create a repo and read back its remote URL:
+
+```ts
+const created = await env.ARTIFACTS.create("starter-repo");
+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
+git clone https://x:${REPO_TOKEN}@artifacts.cloudflare.net/some-namespace/agent-007.git
+```
+
+To learn more, refer to [Get started](/artifacts/get-started/), [Workers binding](/artifacts/api/workers-binding/), and [Git protocol](/artifacts/api/git-protocol/).

src/content/changelog/artifacts/2026-04-16-artifacts-now-in-beta.mdx

@@ -0,0 +1,12 @@
+id: a9X2kP
+name: Artifacts
+
+entry:
+  title: Artifacts
+  url: /artifacts/
+  group: Developer platform
+
+meta:
+  title: Cloudflare Artifacts docs
+  description: Store, version, and share filesystem artifacts across Workers, APIs, and git-compatible tools
+  author: "@cloudflare"

src/content/directory/artifacts.yaml

@@ -0,0 +1,75 @@
+---
+title: Git protocol
+description: Use Artifacts with standard git-over-HTTPS clients.
+pcx_content_type: reference
+sidebar:
+  order: 3
+---
+
+Artifacts exposes Git access for every Artifacts repository.
+
+Each repo has a standard Git smart HTTP remote at `https://{accountId}.artifacts.cloudflare.net/git/{namespace}/{repo}.git`.
+
+Use the returned repo `remote` with a regular Git client for `clone`, `fetch`, `pull`, and `push`.
+
+## Authentication
+
+Git routes accept repo access tokens in two forms:
+
+| Format                             | Details                                                                                                                               | Example                                                                                                      |
+| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
+| Bearer token in `http.extraHeader` | Recommended for local workflows. Use the full token string returned by the control plane and keep credentials out of the remote URL. | `git -c http.extraHeader="Authorization: Bearer $ARTIFACTS_TOKEN" clone "$ARTIFACTS_REMOTE" artifacts-clone` |
+| HTTP Basic auth in the remote URL  | Use for short-lived, one-off commands when you need a self-contained remote. Put the token secret in the password slot.              | `https://x:<token-secret>@<accountId>.artifacts.cloudflare.net/git/<namespace>/<repo>.git`                 |
+
+### Token format
+
+Repo tokens are issued in the control-plane response format `art_v1_<40 hex>?expires=<unix_seconds>`.
+
+### Git `extraHeader` parameter
+
+Git's [`http.extraHeader`](https://git-scm.com/docs/git-config#Documentation/git-config.txt-httpextraHeader) setting lets you attach an HTTP header to git requests.
+
+If you want to use the full token string returned by the API, pass it as a Bearer token:
+
+```sh
+git -c http.extraHeader="Authorization: Bearer $ARTIFACTS_TOKEN" clone "$ARTIFACTS_REMOTE" artifacts-clone
+```
+
+### HTTPS remote with Basic auth
+
+For the URL form, use the token secret in the password slot. Artifacts ignores the Basic auth username.
+
+Use this form only when you need a self-contained remote URL for a short-lived command.
+
+```sh
+export ARTIFACTS_TOKEN_SECRET="${ARTIFACTS_TOKEN%%\?expires=*}"
+export ARTIFACTS_AUTH_REMOTE="https://x:${ARTIFACTS_TOKEN_SECRET}@${ARTIFACTS_REMOTE#https://}"
+```
+
+```sh
+git clone "$ARTIFACTS_AUTH_REMOTE" artifacts-clone
+```
+
+```sh
+git push "$ARTIFACTS_AUTH_REMOTE" HEAD:main
+```
+
+Use any non-empty username in the URL. Artifacts accepts that username but does not otherwise use or log it, so `x` is just a placeholder.
+
+## Protocol support
+
+Artifacts supports Git protocol v1 and v2 for clone and fetch. Git clients negotiate the protocol automatically.
+
+| Operation                         | Git service        | Protocol support | Notes                                                                                                                      |
+| --------------------------------- | ------------------ | ---------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| Clone and fetch                   | `git-upload-pack`  | v1 and v2        | Protocol v2 supports `ls-refs` and `fetch`. Protocol v1 supports normal fetch flows, including shallow and deepen fetches. |
+| Push                              | `git-receive-pack` | v1               | Push uses the standard v1 receive-pack flow.                                                                               |
+| Push over protocol v2             | `git-receive-pack` | Not supported    | Artifacts does not support v2 receive-pack.                                                                                |
+| Optional protocol v1 capabilities | `git-upload-pack`  | Partial          | Some optional v1 capabilities, such as `filter` and `include-tag`, are not supported.                                      |
+
+## Token scopes
+
+| Scope   | Commands                                         | Notes                                                   |
+| ------- | ------------------------------------------------ | ------------------------------------------------------- |
+| `read`  | `git clone`, `git fetch`, `git pull`             | Use for read-only access.                               |
+| `write` | `git clone`, `git fetch`, `git pull`, `git push` | `git push` mutates the repo and requires a write token. |

src/content/docs/artifacts/api/git-protocol.mdx

@@ -0,0 +1,15 @@
+---
+title: API
+description: Reference the Artifacts Workers binding, REST API, and filesystem interfaces.
+pcx_content_type: navigation
+sidebar:
+  order: 5
+  group:
+    hideIndex: true
+---
+
+import { DirectoryListing } from "~/components";
+
+Use the Artifacts API reference to understand the interfaces exposed across Workers, HTTP, and Git-compatible workflows.
+
+<DirectoryListing />