Developer tools
Verirun
record a flow once, replay it on every change, check the backend
- Category
- Developer tools
- Stage
- Beta
- For
- Developers and AI coding-agent users testing web application workflows
About
Verirun records a browser workflow once, replays those exact steps headless on command, and captures the backend logs the replay produced. Deterministic, self-hosted, works alongside AI coding agents.
Features
- Problem
- Manually repeated UI checks are inconsistent and can be flaky.
- How it works
- Records a workflow once, saving its steps and stable selectors, then replays the same steps in the same order with one command.
- Result
- Repeatable workflow validation with a clear pass or fail.
- Why
- The recorded workflow—not a model's visual judgment—defines the test.
- Problem
- A green browser test may conceal server-side failures.
- How it works
- Captures backend logs during the precise replay time window and places them alongside the steps that ran.
- Result
- Teams can investigate backend behavior such as duplicate writes, swallowed exceptions, and failed downstream jobs.
- Why
- UI confirmation alone does not prove persistence, jobs, or auth completed correctly.
- Problem
- Test and log data may be sensitive.
- How it works
- Runs the browser, workflows, log retrieval, and credentials on the user's machine, with no Verirun service in the path.
- Result
- Workflows can target localhost, staging, or production without uploading app data to Verirun.
- Why
- Application data, secrets, and logs remain local.
- Problem
- Coding agents can waste effort clicking through browsers and interpreting screenshots.
- How it works
- Exposes a command-based run with an exit code and structured `logs.json`; `verirun agent` prints command guidance.
- Result
- Agents such as Claude Code can verify changes using a repeatable command.
- Why
- Agents can consume deterministic machine-readable results.
- Problem
- Run output can be difficult to reuse in automation.
- How it works
- Writes structured run logs under `.verirun/` and provides pass/fail output.
- Result
- Workflow evidence is usable in terminal-driven development and automation.
- Why
- Structured files can be read, diffed, or piped into other tooling.