wrangler workflows commands target local dev with --local
Introduced 2026-03-31 · score 0.97
HOW TO USE IT
When developing locally, pass `--local` to a `wrangler workflows` command to target a Workflow in a running `wrangler dev` session. Add `--port <port>` when the session uses a custom port; the default is `8787`.
wrangler workflows list --localwrangler workflows trigger <NAME> '{"key":"value"}' --localwrangler workflows instances pause <NAME> <ID> --local --port 9000WHY THIS HELPS
During local development, inspect or operate a Workflow against a running Wrangler dev session.
BEFORE THIS CHANGE
Without `--local`, Workflows commands target production.
REQUIREMENTS AND LIMITATIONS
- Version: 4.79.0
- --local: Interact with a Workflow in a local `wrangler dev` session; the docs say this requires Wrangler 4.79.0 or greater.
- --port <port>: Port of the local dev session; defaults to `8787`.
- <NAME> (required): Workflow name.
- [PARAMS]: JSON string passed as parameters to the Workflow instance.
- <ID> (required): Workflow instance ID to pause.
- Prerequisite: The `--local` flag requires Wrangler 4.79.0 or greater.
- Prerequisite: A running `wrangler dev` session is required for local targeting.
- The local target is a running `wrangler dev` session.
- Commands continue to target remote production by default.
- The default dev server port is 8787.
FIRST-PARTY EVIDENCE
- https://github.com/cloudflare/workers-sdk/releases/tag/wrangler%404.79.0
- https://developers.cloudflare.com/workers/wrangler/commands/workflows/
Check the installed version and the source before using it. Entry JSON