diff --git a/src/content/changelog/workers/2026-07-09-flagship-automatic-provisioning.mdx b/src/content/changelog/workers/2026-07-09-flagship-automatic-provisioning.mdx
new file mode 100644
index 00000000000..bb48ff89560
--- /dev/null
+++ b/src/content/changelog/workers/2026-07-09-flagship-automatic-provisioning.mdx
@@ -0,0 +1,28 @@
+---
+title: Automatic provisioning for Flagship bindings
+description: Wrangler can now automatically provision Flagship apps when deploying Workers with Flagship bindings.
+products:
+  - workers
+  - flagship
+date: 2026-07-09
+---
+
+import { WranglerConfig } from "~/components";
+
+Wrangler automatic resource provisioning now supports Flagship bindings. Add a `flagship` binding without an `app_id`, and Wrangler can connect an existing Flagship app or create a new one during deployment. Wrangler writes the resulting `app_id` back to your configuration file.
+
+<WranglerConfig>
+
+```jsonc
+{
+	"flagship": [
+		{
+			"binding": "FLAGS",
+		},
+	],
+}
+```
+
+</WranglerConfig>
+
+For more information, refer to [automatic provisioning](/workers/wrangler/configuration/#automatic-provisioning) and [Flagship bindings](/flagship/binding/).
diff --git a/src/content/docs/workers/wrangler/configuration.mdx b/src/content/docs/workers/wrangler/configuration.mdx
index 7ad44c36d05..8ab77f2b1b1 100644
--- a/src/content/docs/workers/wrangler/configuration.mdx
+++ b/src/content/docs/workers/wrangler/configuration.mdx
@@ -104,7 +104,7 @@ Further, there are a few keys that can _only_ appear at the top-level.
 
 Wrangler can automatically provision resources for you when you deploy your Worker without you having to create them ahead of time.
 
-This currently works for KV, R2, and D1 bindings.
+This currently works for KV, R2, D1, and Flagship bindings.
 
 To use this feature, add bindings to your configuration file _without_ adding resource IDs, or in the case of R2, a bucket name. Resources will be created with the name of your worker as the prefix.