feat(wrangler): add wrangler tunnel by thomasgauvin · Pull Request #12492 · cloudflare/workers-sdk

thomasgauvin · 2026-02-09T17:18:46Z

Manage Cloudflare Tunnels

COMMANDS
wrangler tunnel create Create a new Cloudflare Tunnel
wrangler tunnel delete Delete a Cloudflare Tunnel
wrangler tunnel info Display details about a Cloudflare Tunnel
wrangler tunnel list List all Cloudflare Tunnels in your account
wrangler tunnel update Update a Cloudflare Tunnel
wrangler tunnel run [tunnel] Run a Cloudflare Tunnel using cloudflared
wrangler tunnel quick-start Start a free, temporary tunnel without an account (https://try.cloudflare.com)
wrangler tunnel route Configure routing for a Cloudflare Tunnel (DNS hostnames or private IP networks)
wrangler tunnel service Manage cloudflared as a system service
wrangler tunnel cleanup <tunnels..> Remove stale tunnel connections
wrangler tunnel token Fetch the credentials token for an existing tunnel (by name or UUID) that allows to run it

GLOBAL FLAGS
-c, --config Path to Wrangler configuration file [string]
--cwd Run as if Wrangler was started in the specified directory instead of the current working directory [string]
-e, --env Environment to use for operations, and for selecting .env and .dev.vars files [string]
--env-file Path to an .env file to load - can be specified multiple times - values from earlier files are overridden by values in later files [array]
-h, --help Show help [boolean]
-v, --version Show version number [boolean] commands for managing Cloudflare Tunnels
Adds tunnel management commands that align with the cloudflared CLI:

CRUD: create, list, info, update, delete
Runtime: run (with token/token-file support), quick-start (Try Cloudflare)
Routing: route dns, route ip (add/list/delete/get)
Operations: cleanup, token (with --cred-file), service install/uninstall
Includes automatic cloudflared binary download and caching in
~/.wrangler/cloudflared/ with SHA256 verification, platform detection,
and WRANGLER_CLOUDFLARED_PATH override support.

Fixes #[insert GH or internal issue link(s)].

Describe your change...

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:

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

changeset-bot · 2026-02-09T17:18:51Z

🦋 Changeset detected

Latest commit: 41a958f

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

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

vicb · 2026-02-10T07:47:10Z

.changeset/tunnel-commands.md

+
+The `run` and `quick-start` commands automatically download and manage the cloudflared binary, caching it in `~/.wrangler/cloudflared/`. You can override the binary location with the `WRANGLER_CLOUDFLARED_PATH` environment variable.
+
+These commands align with the `cloudflared tunnel` CLI naming conventions.


Huge PR!

Maybe we should start with one/a few commands, do a review and add more later?

Who is the POC on the ANT team for this feature?

These commands align with the cloudflared tunnel CLI naming conventions.

IMO we should rather align with other wrangler commands... or use cloudflared tunnel directly ?

I believe @petebacondarwin is the POC for us. Our Tunnel requirement is that we need to align wrangler commands with cloudflared so that there is no discrepancy between how developers use different Cloudflare CLIs.

vicb · 2026-02-10T07:50:32Z

packages/wrangler/src/tunnel/delete.ts

+		force: {
+			type: "boolean",


Suggested change

force: {

type: "boolean",

force: {

alias: "y",

type: "boolean",

This suggestion will likely break CI as the indentation is wrong. This either needs to be applied manually or have its indentation fixed to match the type property.

vicb · 2026-02-10T07:51:12Z

packages/wrangler/src/tunnel/delete.ts

+export const tunnelDeleteCommand = createCommand({
+	metadata: {
+		description: "Delete a Cloudflare Tunnel",
+		status: "stable",


IMO we should always introduce new feature as experimental first

vicb · 2026-02-10T07:52:12Z

packages/wrangler/src/tunnel/delete.ts

+		logger.log(`Deleting tunnel "${args.tunnel}"`);
+		const tunnelId = await resolveTunnelId(sdk, accountId, args.tunnel);
+		await deleteTunnel(sdk, accountId, tunnelId);


What if the tunnel does not exist?

The API error is passed to the user as is in this case:

✔ Are you sure you want to delete tunnel "player"? This action cannot be undone. … yes Deleting tunnel "player" ✘ [ERROR] "player" is neither the ID nor the name of any of your tunnels

vicb

Thanks for the PR Thomas.

I only took a quick look (description + delete) and added a few comments.

petebacondarwin · 2026-02-10T15:23:50Z

Converting to draft since this PR is to act as a spec for the final commands that are to be landed as part of this feature.

GoncaloGarcia · 2026-02-12T13:47:17Z

.changeset/tunnel-commands.md

+
+Adds a new set of commands for managing Cloudflare Tunnels directly from Wrangler:
+
+- `wrangler tunnel create <name>` - Create a new Cloudflare Tunnel


For these API operation to work the user usually has to run cloudflared login. How does this work here?

API wrapper.

GoncaloGarcia · 2026-02-12T14:08:29Z

.changeset/tunnel-commands.md

+
+- `wrangler tunnel token <tunnel>` - Print the tunnel token (or write credentials JSON with `--cred-file`)
+- `wrangler tunnel cleanup <tunnels...>` - Remove stale tunnel connections
+- `wrangler tunnel service install <tunnel>` / `wrangler tunnel service uninstall` - Install/uninstall cloudflared as a system service


This will also require downloading cloudflared, but it's not mentioned below

jcsf · 2026-02-12T15:21:19Z

.changeset/tunnel-commands.md

+
+- `wrangler tunnel token <tunnel>` - Print the tunnel token (or write credentials JSON with `--cred-file`)
+- `wrangler tunnel cleanup <tunnels...>` - Remove stale tunnel connections
+- `wrangler tunnel service install <tunnel>` / `wrangler tunnel service uninstall` - Install/uninstall cloudflared as a system service


Not sure if this makes sense for wrangler to support. Cloudflared running as a service is more for servers, wrangler is a cli tool for users. This doesn't seem useful

jcsf · 2026-02-12T15:21:56Z

.changeset/tunnel-commands.md

+- `wrangler tunnel cleanup <tunnels...>` - Remove stale tunnel connections
+- `wrangler tunnel service install <tunnel>` / `wrangler tunnel service uninstall` - Install/uninstall cloudflared as a system service
+- `wrangler tunnel route dns <tunnel> <hostname>` - Create a DNS CNAME route to a tunnel
+- `wrangler tunnel route ip add <network> <tunnel>` / `list` / `delete` / `get` - Manage private network routes for WARP


Not sure if this makes sense for wrangler to support. Wrangler will be mostly used by Workers VPC users. Those do not use ip routes in any capacity

jcsf · 2026-02-12T15:22:38Z

packages/wrangler/src/__tests__/tunnel-cloudflared-redaction.test.ts

+			"--credentials-contents",
+			"SECRET_CREDS",
+			"--origincert",
+			"/path/to/cert.pem",


origin cert is something no longer supported so this can be removed

jcsf · 2026-02-12T15:24:18Z

packages/wrangler/src/__tests__/tunnel-cloudflared-redaction.test.ts

+			"run",
+			"--token",
+			"SECRET_TOKEN",
+			"--credentials-contents",


we should drive only to use secret_token, and avoid them using credential files. We can fetch the token from the API's

chungthuang · 2026-02-12T15:25:18Z

packages/wrangler/src/__tests__/tunnel-cloudflared.test.ts

+
+			expect(binPath).toContain(expectedDir);
+
+			if (process.platform === "win32") {


Is win32 the only Windows platform?

chungthuang · 2026-02-12T15:27:09Z

packages/wrangler/src/__tests__/tunnel-credentials.test.ts

+import { decodeTunnelTokenToCredentialsFile } from "../tunnel/credentials";
+
+describe("tunnel token credentials decoding", () => {
+	it("decodes cloudflared-style tunnel token into credentials file shape", () => {


Why does wrangler need to know about the tunnel token format?

jcsf · 2026-02-12T15:29:03Z

packages/wrangler/src/tunnel/client.ts

+		conns_active_at: tunnel.conns_active_at as string | undefined,
+		conns_inactive_at: tunnel.conns_inactive_at as string | undefined,
+		tun_type: tunnel.tun_type as CloudflareTunnelResource["tun_type"],
+		connections: tunnel.connections as CloudflareTunnelResource["connections"],


On the tunnel list endpoint, connections are deprecated and will be removed in the future, so just avoid using it there.

chungthuang · 2026-02-12T15:34:02Z

packages/wrangler/src/tunnel/route/dns.ts

+import { resolveTunnelId } from "../client";
+
+/**
+ * Hostname validation matching cloudflared's implementation.


Does wrangler need to do an extra validation? Can't it let cloudflared do the validation and return any error?

Oh this is not calling cloudflared tunnel route dns. It's calling the API directly.

chungthuang · 2026-02-12T15:38:28Z

packages/wrangler/src/tunnel/route/index.ts

@@ -0,0 +1,10 @@
+import { createNamespace } from "../../core/create-command";
+
+export const tunnelRouteNamespace = createNamespace({


What is a namespace?

chungthuang · 2026-02-12T15:43:40Z

packages/wrangler/src/tunnel/client.ts

+	conns_active_at?: string;
+	conns_inactive_at?: string;
+	tun_type?:
+		| "cfd_tunnel"


For wranlger we only need to care about cfd_tunnel.

chungthuang · 2026-02-12T15:48:34Z

packages/wrangler/src/tunnel/client.ts

+ * Create a new tunnel
+ */
+export async function createTunnel(
+	sdk: Cloudflare,


I'm not familiar with this code base. What is sdk? Is it a cloudflare API client?

chungthuang · 2026-02-12T15:56:51Z

packages/wrangler/src/tunnel/cloudflared.ts

+}
+
+async function getExpectedAssetSha256(assetName: string): Promise<string> {
+	const release = await getGithubRelease(CLOUDFLARED_VERSION);


We should get the latest version.

chungthuang · 2026-02-12T16:04:57Z

packages/wrangler/src/tunnel/cloudflared.ts

+		return cached;
+	}
+
+	const url = `https://api.github.com/repos/cloudflare/cloudflared/releases/tags/${version}`;


Are we worried about hitting GitHub API rate limit?

We actually have a worker called by cloudflared for updates https://github.com/cloudflare/cloudflared/blob/master/cmd/cloudflared/updater/update.go#L29. It takes the OS, arch and current version in query parameters https://github.com/cloudflare/cloudflared/blob/master/cmd/cloudflared/updater/workers_service.go#L64.
This worker uses KV for caching.

Yes please use this to check for versions, its the same API used by cloudflared

chungthuang · 2026-02-12T16:05:39Z

packages/wrangler/src/tunnel/cloudflared.ts

+	if (!response.ok) {
+		throw new UserError(
+			`[cloudflared] Failed to fetch cloudflared release metadata from ${url}\n\n` +
+				`HTTP ${response.status}: ${response.statusText}`


Do we want to return the error message in response body?

chungthuang · 2026-02-12T16:13:29Z

packages/wrangler/src/tunnel/quick-start.ts

+		logger.log(`   You'll get a random *.trycloudflare.com URL to share.`);
+		logger.log(`   The tunnel will stop when you press Ctrl+C.\n`);
+
+		// Spawn cloudflared process with automatic binary management


What does automatic binary management mean?

If wrangler downloads cloudflared for the user, it also auto-updates it. Every invocation queries what the latest cloudflared version is, and if the cached version doesn't match the latest, it downloads the new one.

chungthuang · 2026-02-12T16:15:59Z

packages/wrangler/src/tunnel/update.ts

We don't need this if we only support quick tunnels.

ascorbic · 2026-02-12T16:58:14Z

Love it. It would be great if we could support something like wrangler dev --tunnel, to expose your local wrangler dev server via a tunnel.

petebacondarwin · 2026-02-12T17:31:24Z

Love it. It would be great if we could support something like wrangler dev --tunnel, to expose your local wrangler dev server via a tunnel.

I think that is a nice feature that is sort of orthogonal to this - except that they would both potentially download and run cloudflared.

DevinCarr · 2026-02-12T20:06:28Z

.changeset/tunnel-commands.md

+Additional tunnel tooling:
+
+- `wrangler tunnel token <tunnel>` - Print the tunnel token (or write credentials JSON with `--cred-file`)
+- `wrangler tunnel cleanup <tunnels...>` - Remove stale tunnel connections


This functionality shouldn't be needed as it's a legacy supported command but extremely unlikely to need to be used by current customers.

DevinCarr · 2026-02-12T20:07:55Z

.changeset/tunnel-commands.md

+- `wrangler tunnel create <name>` - Create a new Cloudflare Tunnel
+- `wrangler tunnel list` - List all tunnels in your account
+- `wrangler tunnel info <tunnel>` - Display details about a specific tunnel
+- `wrangler tunnel update <tunnel> --name <new-name>` - Rename a tunnel


I don't imagine customers will really leverage this functionality as you can only adjust the tunnel name. Let's omit it for now and only add it if we get some user requests for it.

DevinCarr · 2026-02-12T20:15:42Z

.changeset/tunnel-commands.md

+
+Additional tunnel tooling:
+
+- `wrangler tunnel token <tunnel>` - Print the tunnel token (or write credentials JSON with `--cred-file`)


We would not like this functionality to be provided for two reasons:

We are hoping to remove this functionality in the future and lean more heavily into proper token management instead of allowing customers to read the token after tunnel creation.

We don't want to restrict our future functionality (described in 1.) by then needing to support this command in wrangler for the lifetime of the wrangler-cli. In cloudflared we support a strict 1 year lifetime for existing cloudflared versions to allow us the capability to make backwards incompatible changes in the future.

The recommended way that we should support running tunnels in wrangler should be:

Create a tunnel (via the command)

Save the secret returned in the ~/.cloudflared directory (the same way that cloudflared does)

Running a tunnel then requires either:

A provided token (as manual input) via wrangler tunnel run --token <token>

Fetching the token from ~/.cloudflared directory via wrangler tunnel run <tunnel> (requires looking up the tunnel id to fetch the right secret from the directory)

Providing token file manually via wrangler tunnel run --token-file <token-file>

DevinCarr · 2026-02-12T20:18:28Z

.changeset/tunnel-commands.md

+
+Additional tunnel tooling:
+
+- `wrangler tunnel token <tunnel>` - Print the tunnel token (or write credentials JSON with `--cred-file`)


--cred-file in wrangler should just be unified to --token-file as there is no reason to rely on the confusing legacy naming that cloudflared uses.

There are two options that should be supported for wrangler tunnel run:

--token <token>

--token-file <token-file>

DevinCarr · 2026-02-12T20:25:16Z

packages/wrangler/src/tunnel/route/dns.ts

+		// PUT /zones/{zoneTag}/tunnels/{tunnelId}/routes
+		const result = await fetchResult<DNSRouteResult>(
+			config,
+			`/zones/${zoneTag}/tunnels/${tunnelId}/routes`,


Instead of using this endpoint, please leverage the standard DNS API to create a CNAME route for the tunnel.

https://developers.cloudflare.com/api/resources/dns/subresources/records/methods/create/

DevinCarr · 2026-02-12T20:26:57Z

packages/wrangler/src/tunnel/delete.ts

+
+		logger.log(`Deleting tunnel "${args.tunnel}"`);
+		const tunnelId = await resolveTunnelId(sdk, accountId, args.tunnel);
+		await deleteTunnel(sdk, accountId, tunnelId);


If there are resources (hostname routes, IP routes) attached to the tunnel, a user will be unable to delete it. Not sure what this error condition will look like in that case.

It passes the error onto the user as is:

✔ Are you sure you want to delete tunnel "play"? This action cannot be undone. … yes Deleting tunnel "play" ✘ [ERROR] A request to the Cloudflare API failed. Cannot delete tunnel because it has Warp routing configured. You can delete the route with `cloudflared tunnel route ip delete`. [code: 1023] If you think this is a bug, please open an issue at: https://github.com/cloudflare/workers-sdk/issues/new/choose

DevinCarr · 2026-02-12T20:39:53Z

packages/wrangler/src/tunnel/client.ts

+): Promise<CloudflareTunnelResource> {
+	return withTunnelPermissionCheck(async () => {
+		const response = (await sdk.zeroTrust.tunnels.cloudflared.create({
+			account_id: accountId,


Every tunnel through this tool should only be creating remotely managed tunnels which requires another field: config_src: "cloudflare". Locally managed tunnels are not the direction that we want to support for this use-case. Future improvements to ingress rule APIs will also go in this direction.

https://developers.cloudflare.com/api/resources/zero_trust/subresources/tunnels/subresources/cloudflared/methods/create/

DevinCarr · 2026-02-12T20:43:15Z

packages/wrangler/src/tunnel/cloudflared.ts

+import type { ChildProcess } from "node:child_process";
+
+// cloudflared version to download
+export const CLOUDFLARED_VERSION = "2026.1.2";


We are pinning a cloudflared version to a wrangler version? Do we instead want to keep the latest version of cloudflared?

DevinCarr · 2026-02-12T20:49:33Z

packages/wrangler/src/tunnel/cloudflared.ts

+		errorMessage += `  - You're missing required system libraries\n`;
+
+		if (process.platform === "linux") {
+			errorMessage += `\nOn Linux, make sure you have the required dependencies:\n`;


What is the error for? When does this happen?

DevinCarr · 2026-02-12T20:51:48Z

packages/wrangler/src/tunnel/cloudflared.ts

+				`  - The version ${CLOUDFLARED_VERSION} doesn't exist\n` +
+				`  - GitHub is temporarily unavailable\n` +
+				`  - You're being rate limited\n\n` +
+				`You can manually download cloudflared from:\n` +


Let's point users to normal client download mechanisms instead of github if we can help it.

DevinCarr · 2026-02-12T20:55:10Z

packages/wrangler/src/tunnel/cloudflared.ts

+		`Spawning cloudflared: ${binPath} ${redactCloudflaredArgsForLogging(args).join(" ")}`
+	);
+
+	const cloudflared = spawn(binPath, args, {


We have the capability to output cloudflared logs as json (--output json), do we want to leverage that here at all, or just dump the standard log lines?

DevinCarr · 2026-02-12T21:00:05Z

packages/wrangler/src/tunnel/cloudflared.ts

+}
+
+const knownPlatforms: Record<string, BinarySpec> = {
+	"darwin arm64 LE": {


Why is the endianness needed?

Manage Cloudflare Tunnels COMMANDS wrangler tunnel create <name> Create a new Cloudflare Tunnel wrangler tunnel delete <tunnel> Delete a Cloudflare Tunnel wrangler tunnel info <tunnel> Display details about a Cloudflare Tunnel wrangler tunnel list List all Cloudflare Tunnels in your account wrangler tunnel update <tunnel> Update a Cloudflare Tunnel wrangler tunnel run [tunnel] Run a Cloudflare Tunnel using cloudflared wrangler tunnel quick-start <url> Start a free, temporary tunnel without an account (https://try.cloudflare.com) wrangler tunnel route Configure routing for a Cloudflare Tunnel (DNS hostnames or private IP networks) wrangler tunnel service Manage cloudflared as a system service wrangler tunnel cleanup <tunnels..> Remove stale tunnel connections wrangler tunnel token <tunnel> Fetch the credentials token for an existing tunnel (by name or UUID) that allows to run it GLOBAL FLAGS -c, --config Path to Wrangler configuration file [string] --cwd Run as if Wrangler was started in the specified directory instead of the current working directory [string] -e, --env Environment to use for operations, and for selecting .env and .dev.vars files [string] --env-file Path to an .env file to load - can be specified multiple times - values from earlier files are overridden by values in later files [array] -h, --help Show help [boolean] -v, --version Show version number [boolean] commands for managing Cloudflare Tunnels Adds tunnel management commands that align with the cloudflared CLI: - CRUD: create, list, info, update, delete - Runtime: run (with token/token-file support), quick-start (Try Cloudflare) - Routing: route dns, route ip (add/list/delete/get) - Operations: cleanup, token (with --cred-file), service install/uninstall Includes automatic cloudflared binary download and caching in ~/.wrangler/cloudflared/ with SHA256 verification, platform detection, and WRANGLER_CLOUDFLARED_PATH override support.

Remove commands not needed for remotely managed tunnels: route (dns/ip), service, cleanup, token, update, and credentials. Enforce token-only auth with config_src:'cloudflare' on create, strip deprecated tunnel types and connections field from the API client. Rewrite cloudflared binary management to use Cloudflare's update worker (update.argotunnel.com) instead of GitHub API, with a GitHub release URL fallback for platforms the update worker doesn't cover (e.g. darwin/arm64). Prompt users before downloading cloudflared, warn when PATH-installed binary is outdated, and pass tunnel tokens via TUNNEL_TOKEN env var instead of --token-file for broader compatibility and security. Mark all tunnel commands as experimental and add subway emoji to the namespace description.

pkg-pr-new · 2026-02-17T15:18:28Z

create-cloudflare

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

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-shared

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

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-pool-workers

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

@cloudflare/workers-editor-shared

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

@cloudflare/workers-utils

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

wrangler

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

commit: 41a958f

- Remove expect from vitest imports in all tunnel test files - Add expect parameter to all test callbacks per workers-sdk/no-vitest-import-expect rule - Fix type annotations to avoid explicit any usage - Use type-only import for CloudflaredModule to avoid forbidden import() type annotation - Remove duplicate test in tunnel-resolve.test.ts

- Fix handler access by casting tunnelRunCommand to any - Add config_src property to mockTunnelCreate return type - Remove duplicate CloudflaredModule import

thomasgauvin requested a review from a team as a code owner February 9, 2026 17:18

vicb reviewed Feb 10, 2026

View reviewed changes

petebacondarwin marked this pull request as draft February 10, 2026 15:23

GoncaloGarcia reviewed Feb 12, 2026

View reviewed changes

jcsf reviewed Feb 12, 2026

View reviewed changes

chungthuang reviewed Feb 12, 2026

View reviewed changes

jcsf reviewed Feb 12, 2026

View reviewed changes

chungthuang reviewed Feb 12, 2026

View reviewed changes

packages/wrangler/src/tunnel/update.ts Outdated

Copy link

chungthuang Feb 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't need this if we only support quick tunnels.

DevinCarr reviewed Feb 12, 2026

View reviewed changes

thomasgauvin and others added 4 commits February 17, 2026 15:08

docs: update tunnel changeset to reflect trimmed command set

d99b3e3

feat: add -y alias for --force on tunnel delete

0288b26

nikitacano force-pushed the tgauvin/wrangler-tunnel-commands branch from 0007853 to 0288b26 Compare February 17, 2026 15:12

workers-devprod added this to workers-sdk Feb 17, 2026

github-project-automation bot moved this to Untriaged in workers-sdk Feb 17, 2026

nikitacano added 3 commits February 17, 2026 15:46

fix: apply prettier formatting to tunnel.test.ts

3c29a6c

fix: resolve TypeScript type errors in tunnel tests

41a958f

- Fix handler access by casting tunnelRunCommand to any - Add config_src property to mockTunnelCreate return type - Remove duplicate CloudflaredModule import


		The `run` and `quick-start` commands automatically download and manage the cloudflared binary, caching it in `~/.wrangler/cloudflared/`. You can override the binary location with the `WRANGLER_CLOUDFLARED_PATH` environment variable.

		These commands align with the `cloudflared tunnel` CLI naming conventions.


		Adds a new set of commands for managing Cloudflare Tunnels directly from Wrangler:

		- `wrangler tunnel create <name>` - Create a new Cloudflare Tunnel


		expect(binPath).toContain(expectedDir);

		if (process.platform === "win32") {

		@@ -0,0 +1,10 @@
		import { createNamespace } from "../../core/create-command";

		export const tunnelRouteNamespace = createNamespace({


		Additional tunnel tooling:

		- `wrangler tunnel token <tunnel>` - Print the tunnel token (or write credentials JSON with `--cred-file`)

Conversation

thomasgauvin commented Feb 9, 2026 • edited by devin-ai-integration bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

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

Uh oh!

🦋 Changeset detected

Uh oh!

vicb Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

vicb left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

petebacondarwin commented Feb 10, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ascorbic commented Feb 12, 2026

Uh oh!

petebacondarwin commented Feb 12, 2026

Uh oh!

thomasgauvin commented Feb 9, 2026 •

edited by devin-ai-integration bot

Loading

changeset-bot bot commented Feb 9, 2026 •

edited

Loading

vicb Feb 10, 2026 •

edited

Loading

vicb left a comment •

edited

Loading

DevinCarr Feb 12, 2026 •

edited

Loading

nikitacano Feb 17, 2026 •

edited

Loading