How it works · Hardware interaction
Build, flash, and watch — in the loop.
Generating code is the easy half. Flash runs the build, flashes the target, and reads what comes back, so firmware and hardware stay in one feedback loop instead of two disconnected steps.
Builds with your toolchain
Runs the build you already use — PlatformIO, ESP-IDF, Zephyr/west, or CMake — and reads the compiler output, warnings and all.
Flashes and watches
Programs the target and streams the serial monitor, so the agent sees what the board actually does after the code lands.
Closes the loop
Build errors and runtime traces feed straight back in as the next iteration — no copy-pasting logs into a fresh prompt.
Why it matters
The bug shows up at runtime — so the loop has to reach runtime.
Most of firmware is the iteration: build, flash, observe, adjust. By living inside your existing build and serial tools, Flash turns each failed build or odd trace into the input for the next attempt — and meets your workflow instead of replacing it.