The CLI-first wireless workflow for Flutter on Android.

Pair, diagnose, connect, and run Flutter applications on Android devices without repeatedly reconnecting a USB cable.

Flutter Android ADB Wireless Debugging VS Code Standalone CLI

English · Français

[!IMPORTANT] Flutter AirRun is CLI-first. The standalone airrun command is the main experience. The VS Code extension installs, opens, updates, and manages it.

Flutter AirRun privilégie la CLI. La commande autonome airrun constitue l’expérience principale. L’extension VS Code l’installe, l’ouvre, la met à jour et la gère.

English

Overview

Flutter AirRun simplifies Android wireless debugging for Flutter development.

Instead of repeatedly finding ADB ports, copying IP addresses, reconnecting phones, and typing several commands, start one interactive tool:

airrun

Flutter AirRun combines:

Architecture

Shared Flutter AirRun Core
ADB · mDNS · Flutter · QR pairing
              │
       ┌──────┴──────┐
       │             │
Standalone CLI   VS Code extension
    airrun       visual companion
       │             │
       └──────┬──────┘
              │
 Android Wireless Debugging

QR sessions are generated directly in TypeScript using secure random data from the runtime. Flutter AirRun no longer requires CMake or a platform-specific QR binary.

Why CLI-first?

The CLI provides:

• one command for the complete workflow;
• an interactive keyboard-driven menu;
• the same experience in VS Code or any terminal;
• direct access to Flutter output and logs;
• standard hot reload and hot restart controls;
• a standalone executable with no Node.js or Bun requirement after installation;
• a clean foundation for automation and scripting.

The VS Code extension remains the installer, launcher, updater, and visual companion for the CLI.

Requirements

You need:

• Flutter available in PATH;
• Android SDK Platform Tools;
• adb available in PATH;
• an Android device with Wireless debugging in Developer options;
• the computer and phone on the same local network;
• a Flutter project containing pubspec.yaml;
• Visual Studio Code only when using the extension.

The installed CLI is standalone. Node.js and Bun are not required after installation.

What the VSIX installs

Each platform-specific VSIX contains one executable:

Linux / macOS
└── airrun

Windows
└── airrun.exe

The QR generator is integrated into the CLI and extension. No additional QR binary is installed.

Installation locations

On Windows, Flutter AirRun can add its installation directory to the user PATH. On Linux and macOS, ~/.local/bin must be available in PATH.

Install a VSIX

Install the package matching your operating system and architecture:

code --install-extension flutter-airrun-<version>-<target>.vsix --force

Example:

code --install-extension flutter-airrun-0.1.0-linux-x64.vsix --force

Then reload VS Code:

1. Open the Command Palette.
2. Run Developer: Reload Window.
3. Open Flutter AirRun from the Activity Bar.

First launch

When the extension activates, it checks whether the AirRun CLI is installed and up to date.

Select Install AirRun CLI, then open a terminal and run:

airrun

VS Code commands:

Flutter AirRun: Open AirRun CLI — Recommended
Flutter AirRun: Install AirRun CLI
Flutter AirRun: Check AirRun CLI
Flutter AirRun: Update AirRun CLI
Flutter AirRun: Uninstall AirRun CLI

Recommended workflow

Inside a Flutter project:

airrun doctor
airrun pair qr
airrun devices
airrun run

Or open the interactive menu:

airrun

Check the environment
        ↓
Enable Wireless debugging
        ↓
Pair by QR code or six-digit code
        ↓
Check available devices
        ↓
Run the Flutter application wirelessly

Android may change the wireless-debugging TCP port between sessions. AirRun tries to recover the current endpoint automatically using ADB and mDNS data.

Interactive CLI

airrun

Menu:

▶  Launch the application wirelessly
▦  Pair a phone with a QR code
#  Pair a phone with a code
✓  Check the environment
◉  Show devices
≋  Check wireless debugging
×  Quit

CLI commands

Examples:

airrun doctor
airrun pair qr
airrun pair code
airrun devices
airrun status
airrun run
airrun run -d 192.168.0.132:46027
airrun run -- --debug

Pair with a QR code

Run:

airrun pair qr

On the Android phone:

1. Open Settings.
2. Open Developer options.
3. Open Wireless debugging.
4. Select Pair device with QR code.
5. Scan the QR code displayed by AirRun.
6. Wait for pairing and connection confirmation.

Flutter AirRun generates the temporary service name and pairing secret locally.

From VS Code, use:

Flutter AirRun: Pair Device with QR Code

Pair with a six-digit code

Run:

airrun pair code

Then enter the address, pairing port, and six-digit code displayed by Android.

Run wirelessly

Open a terminal in the directory containing pubspec.yaml:

airrun run

Target a specific device:

airrun run -d <device-id>

Forward Flutter arguments:

airrun run -- --debug

Standard Flutter controls remain available:

VS Code companion

Diagnostics

airrun doctor

Healthy output:

✓ Flutter
✓ ADB
✓ TypeScript QR generator
✓ Flutter project
✓ Flutter AirRun environment ready

Running doctor outside a Flutter project still validates Flutter, ADB, and the QR generator.

Troubleshooting

airrun is not found

Linux or macOS:

export PATH="$HOME/.local/bin:$PATH"

Add the line to your shell profile, then open a new terminal.

On Windows, run Flutter AirRun: Check AirRun CLI, reinstall when required, and add the managed directory to PATH.

No device is displayed

airrun doctor
airrun status
airrun devices

Check that Wireless debugging is enabled, both devices are on the same network, local-device communication is allowed, and adb devices works.

The phone is paired but offline

Disable and re-enable Wireless debugging, then run:

airrun status
airrun devices

Flutter does not detect the phone

adb devices
flutter devices
airrun doctor

The QR code is not displayed

airrun doctor
airrun pair qr

From VS Code, run:

Flutter AirRun: QR Generator Doctor

Then inspect Output → Flutter AirRun.

The current directory is not a Flutter project

Open the directory containing pubspec.yaml, then run:

airrun

Security and privacy

• Pairing happens locally between the computer and Android device.
• AirRun uses the Android Debug Bridge tools installed on the machine.
• Pairing codes and temporary QR secrets are processed locally.
• Secure random QR session data is generated by the runtime.
• Flutter AirRun does not require a cloud account.
• The extension does not use sudo for CLI installation.
• Disable Wireless debugging when it is not needed.

Platform status

The QR generator is platform-independent. New targets no longer require a separate native build.

Project structure

flutter-airrun/
├── apps/
│   ├── cli/
│   │   ├── src/
│   │   ├── scripts/
│   │   └── dist-bin/
│   └── vscode-extension/
│       ├── src/
│       ├── scripts/
│       └── resources/
├── packages/
│   └── core/
│       └── src/
│           └── wireless/
│               └── qrPairingSessionService.ts
└── artifacts/

Development

pnpm install
pnpm --filter @flutter-airrun/core build
pnpm --filter @flutter-airrun/cli build
pnpm --filter @flutter-airrun/cli build:executables
pnpm --filter flutter-airrun check
pnpm --filter flutter-airrun build
pnpm --filter flutter-airrun package:vsix -- linux-x64

Supported targets:

linux-x64
linux-arm64
win32-x64
win32-arm64
darwin-x64
darwin-arm64

Français

Présentation

Flutter AirRun simplifie le débogage sans fil Android pour le développement Flutter.

Au lieu de rechercher manuellement les ports ADB, recopier des adresses IP, reconnecter les appareils et répéter plusieurs commandes, lancez un seul outil :

airrun

Flutter AirRun réunit :

Architecture

Core Flutter AirRun partagé
ADB · mDNS · Flutter · association QR
              │
       ┌──────┴──────┐
       │             │
 CLI autonome    Extension VS Code
    airrun       compagnon visuel
       │             │
       └──────┬──────┘
              │
 Débogage sans fil Android

Les sessions QR sont générées directement en TypeScript avec des données aléatoires sécurisées. Flutter AirRun ne dépend plus de CMake ni d’un binaire QR propre à chaque plateforme.

Pourquoi privilégier la CLI ?

La CLI apporte :

• une seule commande pour tout le parcours sans fil ;
• un menu interactif piloté au clavier ;
• la même expérience dans VS Code ou un autre terminal ;
• un accès direct aux journaux et à la sortie Flutter ;
• le hot reload et le hot restart habituels ;
• un exécutable autonome sans Node.js ni Bun après installation ;
• une base propre pour l’automatisation.

L’extension VS Code reste l’installateur, le lanceur, le gestionnaire de mises à jour et le compagnon visuel de la CLI.

Prérequis

Vous devez disposer de :

• Flutter accessible dans le PATH ;
• Android SDK Platform Tools ;
• adb accessible dans le PATH ;
• un appareil Android avec le Débogage sans fil ;
• un ordinateur et un téléphone sur le même réseau local ;
• un projet Flutter contenant pubspec.yaml ;
• Visual Studio Code uniquement pour utiliser l’extension.

La CLI installée est autonome. Node.js et Bun ne sont pas nécessaires après l’installation.

Ce que le VSIX installe

Chaque VSIX contient un seul exécutable :

Linux / macOS
└── airrun

Windows
└── airrun.exe

Aucun binaire QR séparé n’est installé.

Emplacements

Installer un VSIX

code --install-extension flutter-airrun-<version>-<cible>.vsix --force

Exemple :

code --install-extension flutter-airrun-0.1.0-linux-x64.vsix --force

Rechargez ensuite VS Code avec Developer: Reload Window.

Première activation

Choisissez Installer la CLI AirRun, puis lancez :

airrun

Commandes VS Code disponibles :

Flutter AirRun: Open AirRun CLI — Recommended
Flutter AirRun: Install AirRun CLI
Flutter AirRun: Check AirRun CLI
Flutter AirRun: Update AirRun CLI
Flutter AirRun: Uninstall AirRun CLI

Parcours recommandé

airrun doctor
airrun pair qr
airrun devices
airrun run

Ou :

airrun

Vérifier l’environnement
        ↓
Activer le débogage sans fil
        ↓
Associer par QR code ou code à six chiffres
        ↓
Vérifier les appareils
        ↓
Lancer l’application Flutter sans câble

CLI interactive

airrun

▶  Lancer l’application sans fil
▦  Associer un téléphone par QR code
#  Associer un téléphone avec un code
✓  Vérifier l’environnement
◉  Afficher les appareils
≋  Vérifier le débogage sans fil
×  Quitter

Commandes

Association par QR code

airrun pair qr

Sur le téléphone :

1. ouvrez Paramètres ;
2. ouvrez Options pour les développeurs ;
3. ouvrez Débogage sans fil ;
4. choisissez Associer l’appareil avec un QR code ;
5. scannez le QR affiché ;
6. attendez la confirmation.

Le nom de service et le secret temporaire sont générés localement.

Depuis VS Code :

Flutter AirRun: Pair Device with QR Code

Association avec un code

airrun pair code

Saisissez ensuite l’adresse, le port d’association et le code à six chiffres affichés par Android.

Lancer Flutter sans câble

airrun run

Appareil précis :

airrun run -d <device-id>

Arguments Flutter :

airrun run -- --debug

Extension VS Code

Diagnostic

airrun doctor

Résultat sain :

✓ Flutter
✓ ADB
✓ Générateur QR TypeScript
✓ Projet Flutter
✓ Environnement Flutter AirRun prêt

Dépannage

airrun est introuvable

Linux ou macOS :

export PATH="$HOME/.local/bin:$PATH"

Ajoutez cette ligne au profil du terminal.

Sous Windows, utilisez Flutter AirRun: Check AirRun CLI, puis ajoutez le dossier géré au PATH.

Aucun appareil n’est affiché

airrun doctor
airrun status
airrun devices

Vérifiez le réseau local, le débogage sans fil et adb devices.

Le téléphone est hors ligne

Désactivez puis réactivez Débogage sans fil, puis lancez :

airrun status
airrun devices

Flutter ne détecte pas le téléphone

adb devices
flutter devices
airrun doctor

Le QR code ne s’affiche pas

airrun doctor
airrun pair qr

Depuis VS Code :

Flutter AirRun: QR Generator Doctor

Consultez ensuite Output → Flutter AirRun.

Le dossier actuel n’est pas un projet Flutter

Ouvrez le dossier contenant pubspec.yaml, puis lancez :

airrun

Sécurité et confidentialité

• L’association s’effectue localement.
• AirRun utilise l’ADB installé sur la machine.
• Les codes et secrets QR temporaires sont traités localement.
• Les données aléatoires sont produites par l’environnement d’exécution.
• Aucun compte cloud AirRun n’est requis.
• L’extension n’utilise pas sudo.
• Désactivez le débogage sans fil lorsqu’il n’est pas utilisé.

État des plateformes

Le générateur QR est indépendant de la plateforme. Aucune compilation native séparée n’est désormais nécessaire.

Structure du projet

flutter-airrun/
├── apps/
│   ├── cli/
│   │   ├── src/
│   │   ├── scripts/
│   │   └── dist-bin/
│   └── vscode-extension/
│       ├── src/
│       ├── scripts/
│       └── resources/
├── packages/
│   └── core/
│       └── src/
│           └── wireless/
│               └── qrPairingSessionService.ts
└── artifacts/

Développement

pnpm install
pnpm --filter @flutter-airrun/core build
pnpm --filter @flutter-airrun/cli build
pnpm --filter @flutter-airrun/cli build:executables
pnpm --filter flutter-airrun check
pnpm --filter flutter-airrun build
pnpm --filter flutter-airrun package:vsix -- linux-x64

Cibles :

linux-x64
linux-arm64
win32-x64
win32-arm64
darwin-x64
darwin-arm64

Author / Auteur

Henry GOSSOU

• GitHub: github.com/Hen17Ry
• LinkedIn: linkedin.com/in/henrygossou

License / Licence

Flutter AirRun is distributed under the MIT License.

Flutter AirRun est distribué sous licence MIT.