DevTunnels CLI not found

Symptom: The sender fails to start with an error like:

  Error: 'devtunnel' is not recognized as a command

or

  DevTunnel CLI not found. Attempting auto-install...

Cause: The devtunnel CLI is not in your PATH.

Resolution:

Cloud Share will attempt to install the DevTunnels CLI automatically. If auto-install fails or you prefer manual installation:

Windows 

  winget install Microsoft.devtunnel

macOS 

  brew install --cask devtunnel

Linux 

  curl -sL https://aka.ms/DevTunnelCliInstall | bash

After installation, open a new terminal window (to pick up the updated PATH) and try again.

  devtunnel --version   # verify installation
cloud-share-sender

Authentication required / token expired

Symptom:

  DevTunnel authentication required.

or the DevTunnels login prompt does not complete.

Cause: You have not authenticated with DevTunnels yet, or your saved OAuth token has expired.

Resolution:

Cloud Share handles re-authentication automatically when it detects an expired token. If the automatic flow fails, force re-authentication with the --reset flag:

  cloud-share-sender --reset

This clears the saved token from preferences.json and prompts you to log in again with Microsoft or GitHub.

ℹ️ Info: DevTunnels tokens expire periodically. If you have not used the sender in a while, --reset is the quickest fix.

Getting more diagnostic information

Run with verbose logging to see detailed output:

  cloud-share-sender --log verbose