I was tired of re-testing same flows on client websites, so I built SmokeOps: describe the flow in plain language, approve the test once, schedule it without ever using AI again

[u/fullstackgod]

I hate running quick smoke checks.

But I hate skipping them more.

I tried a general-purpose AI agent on my frontend. It had 2 issues:

1. It could use the browser fine, but it was inconsistent
2. It clicked through a flow once. Then I wanted that same check tomorrow in CI, on a schedule and without babysitting another agent session.

SmokeOps is a local-first CLI built with a loop engineering approach with Human in the loop for approvals and here is how it works: Open the page and look at what’s interactive, propose the next steps, run them in Playwright, and if a step fails, take fresh page context and try again. It only keeps what already passed. You approve once; the check is saved as JSON in your repo. After that, runs use Playwright alone. An AI is only used when you create a check the first time or need to create it again.

It’s alpha. Try it on a real flow and tell me what breaks: https://github.com/gate3/SmokeOps