WYSIWYG automation for Windows apps

Build Windows UI automation flows visually, run them with confidence.

Fleet Automate helps you create repeatable desktop automation TestFlows with a visual action box, structured flow editor, UI element capture, live execution state, and inspectable logs.

Get started View screenshots
VisualAction builder
ObservableExecution logs
WindowsFlaUI powered
Fleet Automate main window with Action Box, welcome page, output log, and TestFlows panel
Action Box TestFlows Element Capture Undo & Redo Live Logs CLI Sessions AI Agent Loop winauto-cli

Why Fleet Automate

A visual workflow for desktop automation

Design flows from reusable actions, configure each step with focused dialogs, and watch execution state update directly in the UI.

01

Compose TestFlows visually

Drag automation, system, logic, and flow-control actions into ordered TestFlows without writing glue code.

02

Capture real UI elements

Use built-in element capture to identify windows, buttons, inputs, and other controls from running apps.

03

Observe every run

Follow action state, output logs, pause/resume behavior, and flow results from the same workspace.

04

Keep flows portable

Projects and TestFlows are file-based, making them easy to inspect, version, copy, and share.

From idea to execution

Configure automation steps with purpose-built dialogs.

Each action exposes the properties that matter: identifier type, search scope, retry behavior, invoke mode, and dictionary options. The goal is fast setup with fewer hidden assumptions.

Click Element action configuration dialog in Fleet Automate

AI-ready CLI automation

Close the loop from test authoring to automated repair.

Fleet Automate includes CLI capabilities designed for the AI Agent era. An agent can create or modify TestFlows, run automation, inspect results, and iterate on fixes while the UI remains observable for humans.

1

Automated test development

Agents can create projects, add flows, insert actions, and update action properties from command line calls.

2

Automated test execution

Flows can be prepared by CLI and observed in the desktop UI through UI-hosted command sessions.

3

Result analysis

Structured output includes execution mode, payloads, and errors, making it easier for agents to reason about failures.

4

Iterative repair

Agents can refine selectors, update action settings, save projects, and repeat until the TestFlow passes.

FleetAutomate CLI usage

The CLI routes commands to an open Fleet Automate UI session when a matching project is available. If no UI session is found, it falls back to offline file mode and writes directly to project files.

  • UI session mode: visible, collaborative edits inside the running desktop app.
  • Offline mode: project and TestFlow files are updated without opening the UI.
  • Output: table or JSON, including mode as ui-session or offline.
fleetctl testproj show --project D:\demo\sample.testproj
fleetctl testproj create --project D:\demo\sample.testproj --name SampleProject
fleetctl testflow create --project D:\demo\sample.testproj --name calculator_flow
fleetctl testflow tree --project D:\demo\sample.testproj --flow calculator_flow
fleetctl action add --project D:\demo\sample.testproj --flow calculator_flow --type LaunchApplicationAction
fleetctl action set --project D:\demo\sample.testproj --flow calculator_flow --path 0 --property ExecutablePath --value calc.exe
fleetctl action show --project D:\demo\sample.testproj --flow calculator_flow --path 0 --format json
fleetctl project save --project D:\demo\sample.testproj

Companion CLI tool

winauto-cli for UI inspection and selector debugging

winauto-cli is a Python CLI wrapper around pywinauto for Windows desktop automation. It gives agents a command surface for inspection, interaction, validation, screenshots, and path-oriented selector refinement.

PyPI describes commands such as list-windows, find, inspect, act, assert, and screenshot. It requires Python 3.10+.

pip install winauto-cli Open PyPI page

Workflow

Capture. Configure. Run. Inspect.

1

Capture target UI

Capture or type element identifiers and keep reusable targets in project dictionaries.

2

Build the TestFlow

Combine clicks, waits, conditions, loops, logs, variables, and system actions into a readable flow.

3

Run with visibility

Watch completion state, output logs, retries, and pause/resume behavior without losing context.

Fleet Automate TestFlow editor showing completed calculator automation actions

Calculator demo

Readable flows for real Windows applications.

The calculator sample demonstrates a complete UI automation flow: locate the app, invoke buttons, wait for expected UI, and record execution progress.

Getting started

Run Fleet Automate from the repository.

Build the desktop application:

dotnet build src/FleetAutomate.Application/FleetAutomate.csproj

Then open a sample project from:

src/SampleProjects/WindowsCalculatorCli/windows-calculator.testproj

Ready to automate?

Start with the sample Windows Calculator project.

Clone the repository, open the sample project, and inspect a working TestFlow end to end.

Open repository