FluxBench Compiler Companion · Windows preview
Build firmware on your own computer.
Choose Compile → This computer in FluxBench. Your PC builds the firmware and sends it directly back to your browser. Local compilation does not use the cloud compiler or require an AI subscription.
Download for Windows
Windows 10/11 x64. The setup app includes Node.js, installs for your Windows user and adds a Start menu shortcut. No administrator access is required.
Download compiler setup 1.0.3 (.exe)This preview is unsigned; Windows may show an unknown-publisher warning. Signed distribution and fresh-user testing remain pending.
Version 1.0.3 · SHA-256: b12492d659c56287a4fb5a6e74e131a892f91c032abe9c22079b3ab5c40c31eb
Set up once
- Open the downloaded setup app. Select Install Arduino CLI. It downloads the pinned Arduino CLI directly from Arduino and verifies its checksum.
- Select your board family and Install board package. This downloads its compilers and supporting files. Large packages can take several minutes and use gigabytes of disk space. Keep the setup window open.
- Install any libraries your sketch needs using their Arduino Library Manager names, such as
ServoorAdafruit SSD1306. You can enterName@versionfor a specific version. Project library selections do not automatically install software on your PC. - Select Start, then Copy key. In FluxBench, open Compile → This computer, paste the key and choose Connect. Allow FluxBench’s local network access if the browser asks. The connection check reports whether your selected board package is installed at the required version. After installing a missing package, start the companion and choose Recheck connection.
- Select Compile on this computer. Download the resulting firmware using the same controls as a cloud build.
The compiler choice is remembered for your FluxBench account in this browser. The key stays in this tab’s session storage; reconnect in a new session. The compiled Uno Lab also follows this choice. To use the cloud again, explicitly select Cloud.
Board packages in this preview
- Arduino Uno / Nano / Mega / Leonardo / Micro / Pro Mini ·
1.8.8 - ESP32 family (including LilyGO / M5Stack chip targets) ·
3.3.10 - ESP8266 / NodeMCU / D1 mini / ESP-01 ·
3.1.2 - Raspberry Pi Pico / Pico W / Pico 2 ·
5.6.1
Special ESP32 development boards use the same chip targets as FluxBench’s cloud compiler. Their display or sensor libraries still need installation and configuration. Other MCU packages and FPGA synthesis are outside this local preview; they remain available through the cloud where supported.
Firmware compilation does not establish physical board compatibility. Physical controller and PCB testing remain deferred.
Daily use and troubleshooting
Open Start → FluxBench Compiler Companion and select Start. Minimize to leave it running in the system tray. Double-click the tray icon to reopen it. Stop cancels a build or installation; closing the window stops the companion. Automatic startup is not installed.
- Cannot connect: check that this companion is running on the same PC as the browser. Check FluxBench’s local network permission in your browser’s site settings. Current Chrome or Edge is recommended. Do not turn off browser security.
- Missing board or library: stop the companion, install the required package/library, then start it again. This uses a separate package folder from your Arduino IDE.
- Incorrect key: copy the current key and reconnect. Replace key invalidates all previous browser connections. Forget key removes this tab’s stored key.
- Build request does not finish: the Compile dialog cancels its browser request after 5½ minutes and displays an error. Check the companion or connection, then retry. Closing the dialog also cancels its request; remote builds retain their own time limits.
- Local build fails: read the compiler output. FluxBench does not silently send the sketch to the cloud. Select Cloud yourself if you want to try that compiler.
Connection check does not finish
You can cancel a connection check safely. A timeout means the browser could not complete the connection; it does not prove that your compiler is stopped. Confirm the companion is running on the same computer, then retry.
Embedded browsers may not offer the local network permission needed by this compiler. If the request times out without a permission prompt, open fluxbench.ai in your regular Chrome or Edge browser and connect there. Keep browser security enabled. An AI companion showing Connected does not establish that the separate local compiler is reachable.
Older compiler downloads cannot report installed packages. Update the setup app to get that check. A connected package can still need extra libraries for your particular sketch; read the build output if compilation fails.
What stays local
Build requests and firmware travel between this browser and 127.0.0.1:17392. They are not relayed through FluxBench’s servers. Normal project saving, AI assistance and cloud simulation are separate features and still use their configured services. The FluxBench website itself still needs internet.
The companion accepts one build at a time, up to five minutes, 4 MB of source and 32 MB of firmware output. It has no USB, upload or shell-command endpoint. Temporary build folders are removed after each build. Compiler packages run as native software under your Windows user; compile source you trust.
This is separate from the AI companion. You can run either or both, with independent keys and Start/Stop controls.
Remove the companion
Close it, remove its Start menu shortcut and the version folder under %LOCALAPPDATA%\FluxBench.ai2\compiler-desktop. Packages, libraries and the connection key are stored separately in compiler-data. Remove that folder only if you also want to erase those downloads and invalidate its key.
Technical references: Arduino CLI setup · Chrome local network permissions.