Remote Bindings GA

src/content/changelog/workers/2025-09-16-remote-bindings-ga.mdx

@@ -0,0 +1,44 @@
+---
+title: Remote bindings GA - Connect to remote resources (D1, KV, R2, etc.) during local development
+description: You can now connect to R2 buckets, D1 databases, and other resources running on Cloudflare, while running your Worker's code locally, on your own machine.
+products:
+  - workers
+date: 2025-09-16
+---
+
+import { WranglerConfig, Aside } from "~/components";
+
+3 months ago [we announced the public beta](https://developers.cloudflare.com/changelog/2025-06-18-remote-bindings-beta/) of [remote bindings](/workers/development-testing/#remote-bindings) for local development. Now, we're excited to say that it's available for everyone in Wrangler, Vite, and Vitest without using an experimental flag!
+
+With remote bindings, you can now connect to deployed resources like [R2 buckets](/r2/) and [D1 databases](/d1/) while running Worker code on your local machine. This means you can test your local code changes against real data and services, without the overhead of deploying for each iteration.
+
+## Example configuration
+
+To enable remote mode, add `"remote" : true` to each binding that you want to rely on a remote resource running on Cloudflare:
+
+<WranglerConfig>
+
+```jsonc title="wrangler.jsonc"
+{
+	"name": "my-worker",
+	"compatibility_date": "$today",
+
+	"r2_buckets": [
+		{
+			"bucket_name": "screenshots-bucket",
+			"binding": "screenshots_bucket",
+			"remote": true,
+		},
+	],
+}
+```
+
+</WranglerConfig>
+
+When remote bindings are configured, your Worker **still executes locally**, but all binding calls are proxied to the deployed resource that runs on Cloudflare's network.
+
+**You can try out remote bindings for local development today with:**
+
+- [Wrangler v4.37.0](/workers/development-testing/#using-wrangler-with-remote-bindings): Use the `wrangler dev` command.
+- The [Cloudflare Vite Plugin](/workers/development-testing/#using-vite-with-remote-bindings)
+- The [Cloudflare Vitest Plugin](/workers/development-testing/#using-vitest-with-remote-bindings)

src/content/docs/workers/development-testing/index.mdx

@@ -66,6 +66,7 @@ During local development, your Worker code interacts with these bindings using t
 
 - By default, bindings connect to **local resource simulations** (except for [AI bindings](/workers-ai/configuration/bindings/), as AI models always run remotely).
 - You can override this default behavior and **connect to the remote resource**, on a per-binding basis. This lets you connect to real, production resources while still running your Worker code locally.
+- When using `wrangler dev`, you can temporarily disable all remote resources (and connect only to local resources) by providing the `--local` flag (i.e. `wrangler dev --local`)
 
 ## Remote bindings