We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 104 since January 2026, each linked to its source.
wranglerWhen deploying, uploading a version, or creating a preview and you want stack traces mapped to original source, leave `upload_source_maps` unset for Wrangler’s default map generation and upload. Set it to `true` for strict behavior or `false` to opt out; deploy and version upload also accept `--no-upload-source-maps`.
npx wrangler deployTo serve the configured assets directory under a public prefix, set `assets.base_path` to that root-relative path in Wrangler configuration. For authored `200` asset rewrites, include the prefix in both the source and destination paths.
{"assets":{"directory":"./public","base_path":"/docs"}}When exposing a local development server through a Quick Tunnel, pass one or more `--tunnel-allowed-mail` flags to `wrangler dev` to require email authentication.
npx wrangler dev --tunnel --tunnel-allowed-mail <email-or-domain-pattern>When removing secrets from a new Worker version, set each secret’s value to `null` in JSON input, inspect bulk output for created and deleted secrets, then deploy the version to production traffic.
npx wrangler versions secret bulk <secrets.json>When running a local Workflows binding, call object-form `createBatch()` with a count or per-instance options. Read the returned `created` handles and indexed `errors`; the array form remains supported.
const result = await env.<BINDING>.createBatch({ count: 2, params: <payload> });
const handles = result.created;
const errors = result.errors;When a Worker uses Analytics SQL during local development, declare `analytics.binding` in `wrangler.json` and run `wrangler dev`; call it through `env.<BINDING>.query()` without `unsafe.bindings`.
{
"analytics": {
"binding": "ANALYTICS"
}
}When producing events from a Worker to an existing K2 stream, add its ID and a binding name under `k2` in Wrangler config, then call `env.<BINDING>.send(records)` and check `result.success`.
{
"k2": [
{
"binding": "<BINDING>",
"stream": "<32-character-lowercase-hex-stream-id>"
}
]
}When running an interactive shell as a remote command, pass `--tty` before the command to force pseudo-terminal allocation.
wrangler containers ssh <INSTANCE_ID> --tty -- bashWhen a Worker declares a Workflow in `exports`, create it locally with `ctx.exports.<ClassName>.create({ params })`; use `wrangler workflows` with `--local` to trigger or inspect its instances. In Vitest, introspect through a test-only Workflow binding, which also captures instances created via `ctx.exports`.
const instance = await ctx.exports.MyWorkflow.create({ params: { name: "World" } });When deploying or rolling back a Worker with Durable Objects, set the code update mode to control when their code updates. Use `--durable-objects-code-update-mode immediate` for immediate updates, or `deferred <delay>` to set the maximum delay; the Wrangler config field could not be verified in the official docs found.
npx wrangler versions deploy <VERSION-SPECS> --durable-objects-code-update-mode immediate