cloudflared missing

Remote check-in needs cloudflared. Without it, AutoDev serves on the local machine only, and the run does not fail.

What you see #

Remote check-in does not get a public address. When the tunnel cannot start, AutoDev prints this and keeps serving on the local machine:

serve

Tunnel unavailable — serving on loopback only. cloudflared is not installed or not on PATH (...). Install it (winget install --id Cloudflare.cloudflared) and retry.

Nothing else stops. cloudflared is needed only for phone check-in, and the run is unaffected. autodev serve --tunnel prints that message. A server started from the panel writes the same text to the event log as serve.tunnel_failed, and the panel's address line reads Tunnel unavailable — loopback only.

Why #

AutoDev exposes its local plane through a cloudflared quick tunnel, so it needs the cloudflared command on your PATH. A missing binary is the expected first-run case, and AutoDev degrades to a local-only serve instead of failing.

Missing is not the only reason a tunnel fails. The same Tunnel unavailable line carries one of these messages instead:

Message	What it means
`cloudflared did not announce a tunnel URL within 60s`	The tunnel started and never printed its address in 60 seconds.
`cloudflared exited with code N before announcing a URL`	The process ended before it printed an address.
`cloudflared failed: ...`	Starting it raised an error other than a missing file.

Fix #

Install cloudflared, then start the server again:

powershell

winget install --id Cloudflare.cloudflared

powershell

autodev serve --tunnel

The Windows installer is an MSI that needs elevation. AutoDev also reads the AUTODEV_TUNNEL_BIN environment variable: when it is set, it names the binary to run instead of looking on PATH, so a portable executable in a folder of your own works.

Turning remote access on covers the panel's side, and Every CLI command describes serve and its flags.