[wrangler] Experiment: redirect agent-driven static Pages deploys to Workers by MattieTK · Pull Request #14312 · cloudflare/workers-sdk

MattieTK · 2026-06-16T00:54:37Z

Experiment — do not merge.

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: experiment, not intended for release.

changeset-bot · 2026-06-16T00:54:42Z

🦋 Changeset detected

Latest commit: 6455144

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

ask-bonk

I'm Bonk, and I've done a quick review of your PR.

This adds an experimental path that, when Wrangler detects it is being driven by an AI agent, redirects brand-new static pages deploy / pages project create invocations to a Workers static-assets deploy (with fallback to Pages on failure).

Ranked issues:

(High) The user-specified deploy directory is silently dropped on redirect — main(["deploy"]) ignores options.assetsDirectory, so a user running wrangler pages deploy ./dist gets autoconfig guessing the assets dir instead of using ./dist. This can deploy the wrong directory.
(Low) getDetectedAgentId() re-invokes detectAgenticEnvironment a second time (once in isAgenticAgent, once here) per redirect. Minor, but the detection result could be computed once and threaded through.

Noting the PR is explicitly an experiment / do-not-merge, so I've kept this to behavioral correctness rather than polish.

ask-bonk · 2026-06-16T00:56:48Z

+		// Passing no positional path is deliberate — it makes `wrangler deploy`
+		// run autoconfig, which detects the static assets directory and
+		// configures the project for Workers.
+		await main(["deploy"]);


The user's requested assets directory is dropped here. For pages deploy <directory>, options.assetsDirectory holds the directory the user explicitly asked to deploy, but main(["deploy"]) is called with no path and no --assets, so autoconfig will re-detect the assets directory and may pick a different one than the user specified. Forward the directory so the redirect deploys what the user asked for:

Suggested change

await main(["deploy"]);

// Forward the user-specified assets directory (when present) so the

// Workers deploy targets the same files the Pages command would have.

// Without this, autoconfig re-detects the directory and may choose a

// different one than the user requested.

const deployArgs =

options.assetsDirectory !== undefined

? ["deploy", "--assets", options.assetsDirectory]

: ["deploy"];

await main(deployArgs);

ask-bonk · 2026-06-16T00:56:54Z

Review posted successfully to PR #14312.

Summary of what I posted:

A high-severity inline suggestion on redirect-to-workers.ts:78: the user-specified deploy directory (options.assetsDirectory) is dropped when calling main(["deploy"]), so autoconfig re-detects the assets directory and may deploy the wrong one. Suggested forwarding it as --assets.
A low-severity note that detectAgenticEnvironment runs twice per redirect (once in isAgenticAgent, once in getDetectedAgentId).

I acknowledged the PR is an explicit experiment/do-not-merge and kept feedback focused on behavioral correctness.

github run

github-actions · 2026-06-16T00:57:20Z

✅ All changesets look good

…Workers

workers-devprod · 2026-06-16T01:00:22Z

Codeowners approval required for this PR:

@cloudflare/wrangler

Show detailed file reviewers

.changeset/agentic-pages-to-workers-redirect.md: [@cloudflare/wrangler]
packages/wrangler/src/tests/pages/redirect-to-workers.test.ts: [@cloudflare/wrangler]
packages/wrangler/src/tests/utils/detect-agent.test.ts: [@cloudflare/wrangler]
packages/wrangler/src/tests/vitest.setup.ts: [@cloudflare/wrangler]
packages/wrangler/src/deploy/autoconfig.ts: [@cloudflare/wrangler]
packages/wrangler/src/metrics/send-event.ts: [@cloudflare/wrangler]
packages/wrangler/src/pages/deploy.ts: [@cloudflare/wrangler]
packages/wrangler/src/pages/projects.ts: [@cloudflare/wrangler]
packages/wrangler/src/pages/redirect-to-workers.ts: [@cloudflare/wrangler]
packages/wrangler/src/utils/detect-agent.ts: [@cloudflare/wrangler]

devin-ai-integration

Devin Review found 1 potential issue.

devin-ai-integration · 2026-06-16T01:06:38Z

+		const redirect = await maybeRedirectPagesToWorkers({
+			command: "create",
+			projectPath: process.cwd(),
+		});
+		if (redirect.handled) {
+			return;
+		}


🚩 Redirect from pages project create silently discards user-provided project name

When an AI agent runs wrangler pages project create my-app, the handler at packages/wrangler/src/pages/projects.ts:144-150 calls maybeRedirectPagesToWorkers({ command: "create", projectPath: process.cwd() }) — the projectName argument (which is demandOption: true) is not forwarded. The redirect then invokes main(["deploy"]) (redirect-to-workers.ts:78), which runs autoconfig. Autoconfig derives the project name from the directory name, not from the agent's requested name. So wrangler pages project create my-api in a directory named my-project would create a Workers project named my-project, not my-api. This also changes semantics from "create project only" to "create AND deploy". This appears intentional per the changeset description but is worth noting as a potential source of agent confusion.

Was this helpful? React with 👍 or 👎 to provide feedback.

pkg-pr-new · 2026-06-16T01:08:40Z

create-cloudflare

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

@cloudflare/deploy-helpers

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

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-shared

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

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-pool-workers

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

@cloudflare/workers-auth

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

@cloudflare/workers-editor-shared

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

@cloudflare/workers-utils

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

wrangler

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

commit: 6455144

workers-devprod added this to workers-sdk Jun 16, 2026

github-project-automation Bot moved this to Untriaged in workers-sdk Jun 16, 2026

ask-bonk Bot reviewed Jun 16, 2026

View reviewed changes

[wrangler] Experiment: redirect agent-driven static Pages deploys to …

6455144

…Workers

MattieTK force-pushed the experiment/intercept-pages-deploy-redirect-to-workers branch from b241ef5 to 6455144 Compare June 16, 2026 00:57

MattieTK marked this pull request as ready for review June 16, 2026 00:59

MattieTK requested a review from workers-devprod as a code owner June 16, 2026 00:59

MattieTK marked this pull request as draft June 16, 2026 01:00

workers-devprod requested review from a team and NuroDev and removed request for a team June 16, 2026 01:00

devin-ai-integration Bot reviewed Jun 16, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[wrangler] Experiment: redirect agent-driven static Pages deploys to Workers#14312

[wrangler] Experiment: redirect agent-driven static Pages deploys to Workers#14312
MattieTK wants to merge 1 commit into
mainfrom
experiment/intercept-pages-deploy-redirect-to-workers

MattieTK commented Jun 16, 2026

Uh oh!

changeset-bot Bot commented Jun 16, 2026 •

edited

Loading

Uh oh!

ask-bonk Bot left a comment

Uh oh!

ask-bonk Bot Jun 16, 2026

Uh oh!

ask-bonk Bot commented Jun 16, 2026

Uh oh!

github-actions Bot commented Jun 16, 2026 •

edited

Loading

Uh oh!

workers-devprod commented Jun 16, 2026

Uh oh!

devin-ai-integration Bot left a comment

Uh oh!

devin-ai-integration Bot Jun 16, 2026

Uh oh!

pkg-pr-new Bot commented Jun 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

-		await main(["deploy"]);
+		// Forward the user-specified assets directory (when present) so the
+		// Workers deploy targets the same files the Pages command would have.
+		// Without this, autoconfig re-detects the directory and may choose a
+		// different one than the user requested.
+		const deployArgs =
+			options.assetsDirectory !== undefined
+				? ["deploy", "--assets", options.assetsDirectory]
+				: ["deploy"];
+		await main(deployArgs);

Conversation

MattieTK commented Jun 16, 2026

Uh oh!

changeset-bot Bot commented Jun 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🦋 Changeset detected

Uh oh!

ask-bonk Bot left a comment

Choose a reason for hiding this comment

Uh oh!

ask-bonk Bot Jun 16, 2026

Choose a reason for hiding this comment

Uh oh!

ask-bonk Bot commented Jun 16, 2026

Uh oh!

github-actions Bot commented Jun 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

workers-devprod commented Jun 16, 2026

Uh oh!

devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

Uh oh!

devin-ai-integration Bot Jun 16, 2026

Choose a reason for hiding this comment

Uh oh!

pkg-pr-new Bot commented Jun 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

changeset-bot Bot commented Jun 16, 2026 •

edited

Loading

github-actions Bot commented Jun 16, 2026 •

edited

Loading