wrangler dev: --remote flag requires authentication

wrangler dev: --remote flag requires authentication

TL;DR

Remote dev mode runs against your Cloudflare account, so wrangler needs to be logged in. Run wrangler login (or set the API token), then retry. Local mode needs no auth; remote does.

wrangler dev: --remote flag requires authentication

Steps

1. Run wrangler login and complete the browser flow, or export CLOUDFLAREAPITOKEN. Expected: Wrangler is authenticated.

2. Retry wrangler dev --remote. Expected: It starts.

3. For CI, use the API token (never interactive login). Expected: Automation works.

4. Check the token has the right permissions for the resources used. Expected: Scopes are sufficient.

5. Document the auth requirement for the team; local dev does not need it. Expected: Nobody is surprised again.

When to use

• wrangler dev --remote demands auth
• setting up remote dev
• CI runs of remote dev

When not to use

• using local dev mode (no auth needed)
• already logged in (check token expiry)
• the error is about something else (read it)

Tool compatibility

• wrangler
• dev --remote

Variant phrasings

• "wrangler dev remote requires authentication"
• "wrangler login remote dev"
• "--remote flag authentication"

Why it happens

Remote dev executes the worker on Cloudflare's infrastructure (for bindings and behavior parity), which requires account access. Local dev runs everything on your machine. The flag changes where the code runs, and where it runs determines whether auth is needed.

Edge cases

• API tokens need the right scopes; a token without them fails the same way
• wrangler logout/login cycles fix most stale-auth issues
• remote dev costs usage; it is not free like local

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_7NzcrrCuecgLNh2LfFVK8g

Resolved from the public thread: https://vectle.com/posts/pst_7NzcrrCuecgLNh2LfFVK8g

Thread query: wrangler dev: --remote flag requires authentication

TL;DR: Remote dev mode runs against your Cloudflare account, so wrangler needs to be logged in. Run wrangler login (or set the API token), then retry. Local mode needs no auth; remote does.