VISUAL
AUTOMATION
YOUR WINDOWS.
YOUR WORKFLOW.

Local visual workflows. A visible screen. A deliberate next step.

Product

From a picture
to a process.

Build with the app you already use. Visual references tell the workflow what to look for; explicit connections tell it what happens next.

Windows editor showing a visual library, connected workflow steps, and observation controls
Actual Windows editor rendered with an illustrative workflow. This layout preview does not show live automation.
RECOGNITION

Recognize the right detail

Save multiple reference crops per target. Adjust matching thresholds, scales, search regions, and exclusions. Test recognition without sending input.

WORKFLOW

Connect clear decisions

Use conditions, branches, repeats, waits, keyboard input, clicks, routes, jumps, and stop blocks. Connect success, failure, and unknown outcomes.

VISUAL STATES

Know before you act

Group positive evidence into named states. Ambiguous or insufficient evidence stays UNKNOWN; absence alone never proves another state.

RECOVERY

Handle interruptions explicitly

Opt into bounded foreground recovery. Resume only after stable window checks and fresh observations; uncertain delivered input requires review.

CONTROL

Stay in charge

Start deliberately. Pause releases held inputs. F8 latches an emergency stop. A visible status and bounded event log explain what the workflow is doing.

LOCAL PROJECTS

Keep your work portable

Save workflows, original captures, crop metadata, regions, routes, and click areas. Import or export a project archive without an account.

Compatibility depends on your application and screen conditions. The current version requires a visible target window, uses pixel matching, and does not run in a locked or background desktop. Recognition is not rotation- or perspective-invariant.

Missing is a state
of uncertainty.

Design what the workflow should do when a target is not where you expect.

Look for target→ Retry within a limit→ Check recovery state→ Verify expected screenContinue or safely stop

Recovery paths are configured and bounded. The application cannot invent a reliable recovery sequence for an arbitrary screen.

Try the visual explanation