flowproof
Run your AI agent once, keep the recording, and assert against it from then on. flowproof captures the run at the model boundary - every request and every tool-call decision - and serves it back on later runs, so replay makes zero LLM calls. You assert which tools were called, with which arguments, in which order, and which were not. The same engine drives web, desktop and Citrix.
Agents author, a deterministic engine executes. A flow is described in
YAML with natural-language steps, recorded once against the live app, and
replayed deterministically in CI with zero LLM calls. Built agent-native:
every operation returns structured results a program can reason over, and
agents can drive record/run/get_trace/heal over MCP
(pip install flowproof[mcp], run flowproof-mcp).
# calc.flow.yaml
name: Add two numbers
app: calc
steps:
- Type 5
- Press plus
- Type 3
- Press equals
- assert: display shows 8
from flowproof import Flow
flow = Flow("calc.flow.yaml")
flow.record() # performs the flow live, writes the trace
result = flow.run() # deterministic replay -> RunResult
assert result.passed
Or from the shell: flowproof record calc.flow.yaml, then
flowproof run calc.flow.yaml (add --json for the structured report).
The wheel bundles the Rust engine; no separate install. Targets: web
(headless Chromium, any OS), Windows desktop via UI Automation, sap
(SAP GUI Scripting), vision (pixels-only for Citrix/RDP), and api
(no UI — HTTP/SQL assertion flows, any OS).
Status: beta, in active development. Record→replay, model-grounded authoring, healing with reviewable diffs, suites, run recordings, and the MCP server all work and are tested in CI.
Docs and source: github.com/automators-com/flowproof
1 maintainer
Release files for flowproof 0.23.16
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| flowproof-0.23.16.tar.gz | 1.0 MB | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| flowproof-0.23.16-cp39-abi3-win_amd64.whl | CPython 3.9 | abi3 | Windows x86-64 | Details |
| flowproof-0.23.16-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ x86-64 | Details |
| flowproof-0.23.16-cp39-abi3-macosx_11_0_arm64.whl | CPython 3.9 | abi3 | macOS 11.0+ ARM64 | Details |
Total release size: 31.9 MB
Release files / flowproof-0.23.16.tar.gz
| Download URL | flowproof-0.23.16.tar.gz |
|---|---|
| Size | 1.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cfbd61aa1b662f23682b85a21fa65bd3e08864a7be80778dd5b347ea167e1455
|
|
BLAKE2b-256 checksum How to use checksums |
0c7abb56d743215aa118ffa6c72f09161a920f514bb80696e4730cdda28f4f84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency logRelease files / flowproof-0.23.16-cp39-abi3-win_amd64.whl
| Download URL | flowproof-0.23.16-cp39-abi3-win_amd64.whl |
|---|---|
| Size | 11.3 MB |
| Tags | CPython 3.9 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
3d35e0ef4306c11f4ffc5af842a15a8c8f9dc4201dc0ac7abf31abe9a06dcc58
|
|
BLAKE2b-256 checksum How to use checksums |
a977a5e06242813dcd0aeee9b8dec9463b52369ae20001affd50115bdf781914
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency logRelease files / flowproof-0.23.16-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | flowproof-0.23.16-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 10.2 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
862fe83839a54eb513a12ce9e2a7392176f305a5e9aa5fe9e71af3ea14f29755
|
|
BLAKE2b-256 checksum How to use checksums |
ddfb30f74b12ad749c7e2050a2da7f91818639e0b41661be4f65460e9e7adad3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency logRelease files / flowproof-0.23.16-cp39-abi3-macosx_11_0_arm64.whl
| Download URL | flowproof-0.23.16-cp39-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 9.3 MB |
| Tags | CPython 3.9 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
37f1804124b3fa6c4e9869a6a030942140ce808e03fbcbb67632530f38a8905a
|
|
BLAKE2b-256 checksum How to use checksums |
df357aee6b1a5675e2c373cfb949d181d7c87b0a33713bd04294312e43dfb286
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency log
