feat(wrangler): automate names for agent-driven deploys

[NuroDev]

Prevent agent-driven deploys from pausing for Worker and workers.dev subdomain naming.

When Wrangler detects a pure agent environment, it now derives the Worker name from the project, skips autoconfig naming confirmations, and automatically registers a project-derived workers.dev account subdomain on the first deploy. Human-driven deploys retain the existing interactive flow.

Agent-generated Worker names also use the existing collision guard to avoid overwriting an unrelated Worker. Deploy output explains how the user can change both names.

---

• Tests
  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows:
  • Additional testing not necessary because:
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: This only changes agent-specific prompt behavior, and Wrangler's deploy output explains how to change the generated names.

A picture of a cute animal (not mandatory, but encouraged)

[changeset-bot]

🦋 Changeset detected

Latest commit: 06bf48f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
wrangler	Minor
@cloudflare/vite-plugin	Patch
@cloudflare/vitest-pool-workers	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

✅ All changesets look good

[ask-bonk]

Review posted successfully to PR #14907.

Summary: I reviewed the PR and found one actionable issue — the automatic workers.dev subdomain registration (props.autoRegisterWorkersDevSubdomain) is gated on detectedAgent.isAgent alone rather than shouldUseProjectName. When an agent deploy provides an explicit Worker name (via --name or config), this causes (1) a subdomain/worker-name mismatch and (2) a silent, effectively irreversible account-wide subdomain registration the user didn't opt into. Posted a suggestion to gate on shouldUseProjectName instead.

github run

[pkg-pr-new]

@cloudflare/autoconfig

npm i https://pkg.pr.new/@cloudflare/autoconfig@14907

@cloudflare/config

npm i https://pkg.pr.new/@cloudflare/config@14907

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@14907

@cloudflare/deploy-helpers

npm i https://pkg.pr.new/@cloudflare/deploy-helpers@14907

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@14907

miniflare

npm i https://pkg.pr.new/miniflare@14907

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@14907

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@14907

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@14907

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@14907

@cloudflare/workers-auth

npm i https://pkg.pr.new/@cloudflare/workers-auth@14907

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@14907

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@14907

wrangler

npm i https://pkg.pr.new/wrangler@14907

commit: 06bf48f

[workers-devprod]

Codeowners approval required for this PR:

• ✅ @cloudflare/wrangler

Show detailed file reviewers

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

[workers-devprod]

Codeowners reviews satisfied