Know what to expect.

The desktop editor uses visual references and connected blocks. You still define the logic, including what should happen on failure or uncertainty.

The current capture and input system requires a visible, unobstructed target window. It does not operate on a locked desktop or a minimized target.

It matches saved image crops against visible pixels. Appearance, scaling, lighting, layout, and similar-looking objects can affect results. It does not understand arbitrary screens.

Configure positive visual states and explicit success, failure, and unknown paths. Bounded foreground recovery can handle certain interruptions after fresh safety checks.

Move the floating controls clear of the reference and click areas, then move the pointer off the menu. The active run rechecks the window and continues only after fresh checks pass; do not press Start while it waits. You can instead choose Stop, inspect the scene and start again deliberately. An uncertain input action is not automatically replayed. The editor labels this state OVERLAY WAIT.

Read the first-run troubleshooting guide.

The desktop engine runs locally and has no screenshot-upload path. This public preview has no custom analytics collection.

F8 is a required emergency stop. Pause and Stop also release tracked held inputs. An event already delivered to Windows cannot be recalled.

The project includes a controlled simulation for learning. Compatibility with a live game is unverified. Only automate where the game or service permits it; there is no anti-cheat bypass.

No. Paid plans, prices, and advanced capabilities are proposals. Checkout remains unavailable until the features, business details, policies, and billing tests are ready.