VS Code and Android Studio

minikit create (or minikit ide setup in an existing project) writes launch configurations for both IDEs. They contain no machine-specific paths: they run the project's .minikit/minikit launcher, which points at your toolkit checkout and is git-ignored.

VS Code

Choose Mini App Simulator in Run and Debug and press F5. The Dart extension runs minikit in place of flutter (its customTool setting), so the app opens in the simulator, saving hot-reloads, the restart button hot-restarts, and DevTools attaches. Mini App Simulator (Chrome) does the same through Chrome. For breakpoints use Flutter's own Chrome device.

If your launch.json has comments, ide setup leaves it alone and prints the entries to add.

Android Studio / IntelliJ

The Flutter plugin cannot replace the flutter command, so the configuration works the other way round: Mini App Simulator runs Flutter itself on the web-server device at the project's port, and a before launch step (Mini App Simulator (attach), a shell-script configuration) asks the simulator to show that port. The simulator waits for Flutter to serve the app, so the order does not matter. Hot reload and restart are the IDE's own buttons; DevTools works; breakpoints need Flutter's Chrome device.

Environment variables the launch configurations use