|
| 1 | +--- |
| 2 | +title: "No config? No problem. Just wrangler deploy" |
| 3 | +description: Automatic project configuration is now the default behavior of wrangler deploy, with support for automatic pull requests in the Cloudflare dashboard. |
| 4 | +products: |
| 5 | + - workers |
| 6 | +date: 2026-02-10 |
| 7 | +--- |
| 8 | + |
| 9 | +In December 2025, we [introduced automatic configuration](/changelog/2025-12-16-wrangler-autoconfig/) as an experimental feature that detects your framework and configures your project for Cloudflare Workers. Starting with Wrangler **TODO_VERSION**, [automatic configuration](/workers/framework-guides/autoconfig/) is now the default behavior of [`wrangler deploy`](/workers/wrangler/commands/#deploy). |
| 10 | + |
| 11 | +## What's new |
| 12 | + |
| 13 | +### Using Wrangler locally |
| 14 | + |
| 15 | +When you run [`wrangler deploy`](/workers/wrangler/commands/#deploy) in a project directory without a [Wrangler configuration file](/workers/wrangler/configuration/), Wrangler will automatically detect your framework and prompt you to confirm the detected settings. Once you confirm, Wrangler will install any required adapters, generate a `wrangler.jsonc` configuration file, and deploy your project to Cloudflare Workers. |
| 16 | + |
| 17 | +You no longer need to pass the `--x-autoconfig` flag. This is now the default behavior. You can also use [`wrangler setup`](/workers/wrangler/commands/#setup) to configure your project without deploying, or pass the [`--yes` flag](/workers/wrangler/commands/#deploy) to skip confirmation prompts. |
| 18 | + |
| 19 | +### Using the Cloudflare dashboard |
| 20 | + |
| 21 | + |
| 22 | + |
| 23 | +When you import a Git repository through the Cloudflare dashboard without a Wrangler configuration file, the deploy command (`wrangler deploy`) triggers [automatic configuration](/workers/framework-guides/autoconfig/) non-interactively. This detects your framework, creates the necessary configuration, and opens a [pull request](/workers/ci-cd/builds/automatic-prs/) for you to review. This PR includes: |
| 24 | + |
| 25 | +- A `wrangler.jsonc` [configuration file](/workers/wrangler/configuration/) |
| 26 | +- Any required framework adapters |
| 27 | +- Updated `package.json` scripts |
| 28 | +- A [preview deployment](/workers/configuration/previews/) so you can test before merging |
| 29 | + |
| 30 | +Once you merge the PR, your project is fully configured and future builds will deploy normally. Refer to [Automatic pull requests](/workers/ci-cd/builds/automatic-prs/) for more details. |
| 31 | + |
| 32 | +:::note |
| 33 | +Automatic pull requests are only created when your deploy command is `npx wrangler deploy`. If you have a custom deploy command, automatic configuration will still run and configure your project, but no PR will be created. |
| 34 | +::: |
| 35 | + |
| 36 | +## Get started |
| 37 | + |
| 38 | +To deploy an existing project to Cloudflare Workers: |
| 39 | + |
| 40 | +```sh |
| 41 | +npx wrangler deploy |
| 42 | +``` |
| 43 | + |
| 44 | +Or import your repository directly from the [Workers dashboard](https://dash.cloudflare.com/?to=/:account/workers-and-pages/create) and get a PR with the generated configuration to review and merge. |
| 45 | + |
| 46 | +If you have questions or run into any issues, join the [GitHub discussion](https://github.com/cloudflare/workers-sdk/discussions/11667). |
0 commit comments