Here’s the most relevant entry I found related to running a plan:
“Flux Execution Plan
Flux creates a step-by-step plan before making changes — so you’re always in control.
Flux outlines all proposed modifications before executing them in the editor. This gives you complete visibility into what’s about to happen and the chance to review, adjust, or reject any part of the plan.
How it works
Initiate a task
Start by asking Flux to make a change — like Make me a usb-c device with bluetooth connectivity powered by the USB bus. I want to connect it directly to a usb port, and use it as a BLE dongle.
Flux responds with a plan
Before applying any changes, Flux will generate a plan. This plan includes all the design actions Flux intends to take.
Review the plan
Read through the proposed steps. Each one is explained clearly and linked to the part of the design it affects. You can expand steps for more details or collapse them to scan quickly.
Edit or reject parts of the plan
Use the chat to suggest changes to the plan, or provide additional context. You can also reject the whole plan if it’s off track.
Approve to execute
Once you’re happy with the plan, hit Start. Flux will carry out the changes in the Flux Editor exactly as described — no surprises.”
Design an 8x32 grid panel of APA-102-2020-256-8 LEDs (256 in total) with complete per-LED decoupling, a single board-level bulk capacitor, and input/output connectors that allow chaining data, clock, and power to both an ESP32 and to subsequent panels.