2.9.30
Released 8 Nov 2026
Official FlowLatch website
End to end testing where an agent runs your suite
FlowLatch 2.9.30 is a Windows agent for people who build and test their own sites. It edits your test files, runs your test command and shows every result as a card in the chat.
The checkout test fails now and then. Find the cause, fix it and run the suite again.
- glob
tests/checkout*3 matches - read_file
tests/checkout.test.tsloaded - Shell
your test commandexit 1 - ocr
reports/checkout-fail.pngtext read - edit_file
tests/checkout.test.tssaved - Shell
your test commandexit 0
waiting for your OK before the next stepRejectAccept
34 MB
Setup program
13
Interface languages
Windows 10/11
For x64 PCs
3
Auto-run, Ask first, Plan only
None
Not needed to run the app
How end to end testing works in FlowLatch
End to end testing walks through one whole user flow, such as sign in, search and checkout, in a real browser against a test copy of your app. FlowLatch has no browser driver. Your own test framework drives the browser, and FlowLatch runs that framework through Shell, reads the real exit code and edits the test files in your working folder on Windows 10 or 11.
Fix a flaky checkout test
Find, then fix. FlowLatch uses grep to locate the selector that fails and read_file to open the test, then Shell runs your test command so the exit code you see is the real one. If your framework saved a failure screenshot, ocr reads the text in it. Ask first pauses before edit_file changes the selector, and the diff shows the line that moves from page layout to a stable test id. You accept, and Shell runs the suite 1 more time.
Tool trace
grep tests/checkout.test.ts → 3 matches
read_file tests/checkout.test.ts → loaded
edit_file tests/checkout.test.ts → saved
Shell your test command → exit 0Run browser automation tools from the chat
FlowLatch does not click anything itself. The browser automation tools you choose drive the browser, and FlowLatch runs them through Shell on Windows 10 or 11, then shows the real exit code and the full output on the card. list_dir finds the tests. Plan only writes the steps without running any, which suits a first look at an unfamiliar project, while Ask first and Auto-run carry out those steps once you switch.
Tool trace
list_dir tests/ → listed
Shell your test command → exit 0
grep FAIL → 0 matchesKeep a growing suite maintained
Web browser automation suites grow. For many teams e2e test maintenance becomes a full time job, because each layout change breaks a selector somewhere. FlowLatch uses glob to list the test files, grep to find selectors tied to page layout, and edit_file to move them to stable labels or test ids. Cron can run a prompt on a schedule, and Ask first, 1 of the 3 approval modes, shows each change as a diff before it is written.
Write a sign-in test with a test inbox
Start with a plain outline. write_file creates a test file for the sign-in flow in your repository, using a test account and fake data. To handle emails in automated e2e tests, point the flow at a test inbox that you set up for the test, never at a real person's mailbox. Shell runs the file with your test command, and the card shows the exit code. Read the diff in Ask first before you accept the 1 new file.
How FlowLatch differs from a chat assistant
FlowLatch acts, not just advises. A typical chat assistant describes a fix in text, while version 2.9.30 runs the command, shows the exit code and writes the file you approve.
| Typical chat assistant | FlowLatch | |
|---|---|---|
| Action | Describes what you could do | Runs the tool and shows a card |
| Result | Text you must run and check yourself | The real exit code of your command |
| Files | Pastes code into the chat | Writes the file and shows a diff |
| Control | No approval step | Auto-run, Ask first or Plan only |
How to get started on Windows
- Download the 34 MB setup program and compare its SHA-256 checksum with the published manifest.
- Run the setup on Windows 10 or 11. If SmartScreen warns, choose More info, then Run anyway, only after the checksum matches.
- Open FlowLatch, connect a cloud model, a local model or the built-in model, and choose your project folder.
- Ask for one flow, such as a sign-in test, and review every card and diff before you accept.
Who uses it and when
Solo developers are the first group. Many solo devs automate e2e testing alone, so the diff that FlowLatch shows before each edit works as a second pair of eyes on a flow that must never break. Reviewing stays yours.
Small teams come next. Teams that already chose their end to end testing tools keep the flows as plain files in the repository, and FlowLatch repairs a selector after a layout change while they read the diff. Tests stay plain files. The interface speaks 13 languages.
Beginners can learn too. Every card shows the command, its real output and the exit code, so you see what a test run actually does on Windows 10 or 11 before you write more of them.
Common questions
What is end to end testing?
End to end testing is a check of one whole user flow, such as sign in, search and checkout, run in a real browser against a test copy of your app. Keep it small. These tests are slower and more fragile than unit tests, so use them for the few flows that must never break.
Is testflowy.com the official FlowLatch website?
Yes, testflowy.com is the official FlowLatch website. Download the 34 MB setup program from the download page and compare its SHA-256 checksum with the published manifest before you run it. Check the checksum. FlowLatch is independent and not affiliated with any testing framework or browser maker, and the Send feedback button inside the app reaches us.
Does FlowLatch drive the browser itself?
No. FlowLatch has no browser driver and cannot watch the screen live. Browser automation is done by the test framework you choose, which FlowLatch runs through Shell on your own PC, reading the output and the exit code. The agent edits the test files, and your framework does the clicking.
Which approval mode should I use for tests?
Ask first is the mode to start with, because it pauses before any action that changes something and shows the diff you accept or reject. Auto-run acts at once and suits flows you have already reviewed. Plan only writes a plan and runs nothing. Switch modes any time.
Do my files leave the PC?
The answer depends. With a cloud model, your prompt, including the text of files the agent reads, goes to that provider. With a local model nothing leaves the PC. Chats, working folders and API keys stay on the PC, and secrets in tool output are redacted before they reach the model.
How does FlowLatch help with a flaky test?
A flaky test is one that passes and fails with no change in the code. FlowLatch repeats the failing test with your test command so the exit code shows whether it is flaky, then looks for the usual causes: fixed waits, selectors tied to page layout, shared test data and tests that depend on each other's order. You decide.
Which Windows versions does FlowLatch support?
The app supports Windows 10 and 11 on x64 PCs, with an interface in 13 languages. No account is needed. The setup program is about 34 MB, version 2.9.30 was released on 8 Nov 2026, and the Update button appears in the app when a newer version is ready to install.
Try it on your own staging app
Download FlowLatch 2.9.30 for Windows 10 or 11. The 34 MB setup program needs no account, and your first run can be a single test file in a folder you own. Start small.
Download FlowLatch for Windows ↗More about FlowLatch
Every page of this website is available in 20 languages.
What FlowLatch can do ↗ Connect a model ↗ Step-by-step testing guide ↗ Download and verify the setup ↗ Questions and answers ↗ Privacy and data ↗
