OPEN SOURCE
Flowproof
A generic open-source automation framework for the AI-agent era: automated testing and agentic process automation across web, desktop, and Citrix. Agents author flows from natural-language intent; a deterministic engine executes them.
pip install flowproof npx flowproof A lineage, continued
Every era of software delivery produced an open-source automation framework that fit how software was built. Flowproof continues that lineage for teams whose flows are authored by developers and their AI agents.
- 2004 Selenium
- 2008 Robot Framework
- 2020 Playwright
- 2026 Flowproof
What it does today
Agents author, a deterministic engine executes
A flow is written as natural-language YAML. An agent performs it once against the live app and records a trace. Replays run the trace with zero model calls: same steps, same selectors, every time.
Web, desktop, and Citrix
One grammar drives browsers over CDP, Windows applications over UI Automation, SAP GUI over its scripting API, and pixel-only surfaces such as Citrix through the vision mode.
Selector ladder with reviewable healing
Each step records native id, structural, and text-anchor selectors. Replay walks the ladder deterministically. When the app truly changed, healing proposes a diff for human review, never a silent mutation.
Testing the whole system, not just pixels
Element, text, and visual assertions with mask regions, plus out-of-band SQL and API probes, because the posted record is often the truth an enterprise test must verify.
Secrets never enter the trace
Values are referenced as ${VAR} and resolved at the moment of use, at record and at every replay. Frames are redacted, password fields always.
Built for CI
Suites with shared browsers, retries, seed and cleanup hooks, JUnit XML, HTML reports, and a recording of every run. Network mocks and browser emulation travel inside the trace so record and replay stay equivalent.
Flowproof is a young project under active development. The trace format is versioned, releases are frequent, and the design notes record what is built, what is planned, and what was deliberately rejected.
Written for developers and their agents
Flows are plain YAML an agent can write and a reviewer can read. The MCP server lets any coding agent record, run, and heal flows, and the complete documentation is published as a single machine-readable file for agents to load in one request.