[wrangler] Add local wrangler commands for Workflows

package.json

@@ -45,7 +45,7 @@
 		"@astrojs/starlight-docsearch": "0.7.0",
 		"@astrojs/starlight-tailwind": "5.0.0",
 		"@cloudflare/vitest-pool-workers": "0.10.7",
-		"@cloudflare/workers-types": "4.20260317.1",
+		"@cloudflare/workers-types": "4.20260331.1",
 		"@expressive-code/plugin-collapsible-sections": "0.41.3",
 		"@expressive-code/plugin-line-numbers": "0.41.3",
 		"@floating-ui/react": "0.27.16",
@@ -139,7 +139,7 @@
 		"unist-util-visit": "5.0.0",
 		"vite-tsconfig-paths": "5.1.4",
 		"vitest": "3.2.4",
-		"wrangler": "4.75.0"
+		"wrangler": "4.79.0"
 	},
 	"engines": {
 		"npm": "11.9.0",

src/content/changelog/workflows/2026-04-01-wrangler-workflows-local.mdx

@@ -0,0 +1,24 @@
+---
+title: All Wrangler commands for Workflows now support local development
+description: Use wrangler workflows commands with the --local flag to manage Workflows running in a local wrangler dev session.
+products:
+  - workflows
+  - workers
+date: 2026-04-01 12:00:00 UTC
+---
+
+All `wrangler workflows` commands now accept a `--local` flag to target a Workflow running in a local `wrangler dev` session instead of the production API.
+
+You can now manage the full Workflow lifecycle locally, including triggering Workflows, listing instances, pausing, resuming, restarting, terminating, and sending events:
+
+```sh
+npx wrangler workflows list --local
+npx wrangler workflows trigger my-workflow --local
+npx wrangler workflows instances list my-workflow --local
+npx wrangler workflows instances pause my-workflow <INSTANCE_ID> --local
+npx wrangler workflows instances send-event my-workflow <INSTANCE_ID> --type my-event --local
+```
+
+All commands also accept `--port` to target a specific `wrangler dev` session (defaults to `8787`).
+
+For more information, refer to [Workflows local development](/workflows/build/local-development/).

src/content/docs/workers/wrangler/commands/workflows.mdx

@@ -14,4 +14,12 @@ The `wrangler workflows` command requires Wrangler version `3.83.0` or greater.
 
 :::
 
+:::note[`--local` option]
+All `wrangler workflows` commands support the `--local` flag to target a Workflow running in a local [`wrangler dev`](/workers/wrangler/commands/general/#dev) session instead of production. Use `--port` to specify the port of the dev session (defaults to `8787`).
+
+The `--local` flag requires Wrangler version `4.79.0` or greater.
+
+For more information, refer to [Workflows local development](/workflows/build/local-development/).
+:::
+
 <WranglerNamespace namespace="workflows" />

src/content/docs/workflows/build/local-development.mdx

@@ -51,8 +51,34 @@ Local development sessions create a standalone, local-only environment that mirr
 
 Refer to the [`wrangler dev` documentation](/workers/wrangler/commands/general/#dev) to learn more about how to configure a local development session.
 
+## Manage Workflows locally
+
+:::note
+The `--local` flag for `wrangler workflows` commands requires Wrangler version `4.79.0` or greater. Use `npx wrangler@latest` to always use the latest version.
+:::
+
+While a `wrangler dev` session is running, you can use all [`wrangler workflows` commands](/workers/wrangler/commands/workflows/) with the `--local` flag to interact with your local Workflow instances.
+
+For example, to list your local Workflows:
+
+```sh
+npx wrangler workflows list --local
+```
+
+To trigger a Workflow locally:
+
+```sh
+npx wrangler workflows trigger my-workflow --local
+```
+
+To inspect a specific instance:
+
+```sh
+npx wrangler workflows instances describe my-workflow <INSTANCE_ID> --local
+```
+
+All commands accept `--port` to target a specific `wrangler dev` session (defaults to `8787`).
+
 ## Known Issues
 
 Workflows are not supported as [remote bindings](/workers/development-testing/#remote-bindings) or when using `npx wrangler dev --remote`.
-
-Wrangler Workflows commands `npx wrangler workflow [cmd]` are not supported for local development, as they target production API.

src/content/release-notes/workflows.yaml

@@ -3,6 +3,14 @@ link: "/workflows/reference/changelog/"
 productName: Workflows
 productLink: "/workflows/"
 entries:
+  - publish_date: "2026-04-01"
+    title: "All wrangler workflows commands now support local development"
+    description: |-
+      All `wrangler workflows` commands now accept a `--local` flag to target a Workflow running in a local `wrangler dev` session. You can now manage the full Workflow lifecycle locally, including listing, triggering, deleting Workflows, and managing instances (list, describe, pause, resume, restart, terminate, and send events).
+
+      All commands also accept `--port` to target a specific `wrangler dev` session (defaults to `8787`).
+
+      More information available in the [changelog](/changelog/2026-03-31-wrangler-workflows-local/).
   - publish_date: "2026-03-26"
     title: "JavaScript Workflows steps can now return streamed output"
     description: |-