Record
Capture clicks, inputs, navigation, selector candidates, and redacted request context from a Chrome extension.
Chrome recorder and replay evidence
TraceFlo records real Chrome sessions and exports a local evidence bundle: JSON, snapshots, action frames, selector candidates, redacted network fingerprints, and a replay plan.
Authenticate in the TraceFlo app when you are ready to connect GitHub sync after a recording.
Runner schema and selector hardening are still being shaped with tester traces.
How it works
TraceFlo keeps the tester's intent, browser evidence, and replay plan together so failures can be reviewed without guessing which step drifted.
Capture clicks, inputs, navigation, selector candidates, and redacted request context from a Chrome extension.
Save local JSON artifacts, PNG snapshots, action frames, network fingerprints, and a replayPlan.
Use the generated plan as the basis for Playwright replay while the runner contract is still being hardened.
Classify failures as selector drift, test data drift, timing, API failure, or product behavior change.
GitHub sync
TraceFlo keeps capture local by default. When a recording is ready to share, sign in to connect a GitHub destination and upload the flow JSON with its snapshots.
Use the Chrome extension to capture browser-heavy flows and build the local JSON artifact with PNG snapshots.
Sign in with GitHub only when you want TraceFlo to sync a finished recording.
Choose the GitHub repository destination and project folder that should receive the generated flow evidence.
Send the clean flow JSON and snapshot assets to GitHub after the local export is complete.
Authorize GitHub, choose a repository, and keep completed recordings organized by project.
Open app