This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
qpilot
Run your manual test cases in a real browser — no code
qpilot is an open-source AI agent that runs your plain-text QA test cases in a real Chrome browser. Paste your steps → hit Run → watch pass/fail/warn per step stream live. If it hits a captcha or OTP, it pauses and asks you directly, then continues. No Playwright scripts. No selectors to maintain. Works with Claude or any OpenAI-compatible model.
I built qpilot because I was tired of watching QA teams (and myself) click through the same test cases release after release — while "proper" automation kept breaking on every UI change and needed a developer to maintain.
qpilot takes a different path: you paste your manual test case as plain text, and an AI agent opens a real Chrome browser and walks through the steps itself. You watch pass / fail / warn appear live for each step. When it hits a captcha or OTP, it doesn't die — it pauses and asks you, then continues.
What makes it different:
🧠 Reads the page like a human — via ARIA semantics, not CSS selectors, so it survives UI changes
📝 Anyone can write tests — if you can write a step-by-step description, you can automate it
⏸️ Human-in-the-loop — captchas and 2FA pause the run instead of killing it
📂 Batch mode — point it at a folder of .md test cases and run them all
🔓 Open source (MIT) — bring your own model: Claude or any OpenAI-compatible endpoint (Qwen, Ollama, vLLM)
Try it in one command:
npx qpilot
I'd love your honest feedback — especially: where would this break in YOUR testing workflow? What's the one feature that would make you actually adopt it?
How does it handle dynamic content or pages where elements shift around, since it sounds like theres no selector layer to anchor onto?
The captcha/OTP pause-and-ask flow is genuinely clever, way more thoughtful than the usual "just mock it" approach other tools take.
The pause-and-ask flow for captchas and OTPs is genuinely clever, that kind of human-in-the-loop handoff is usually the thing that breaks these tools. Love that it's plain-text steps instead of forcing you to maintain selectors.
How well does it handle dynamic content like elements that load after a delay or popups that appear mid-flow?
Does the "plain text" QA steps need to be in any specific format, or can it interpret the messy step-by-step docs my PM writes in Confluence?
how does it handle dynamic content like lazy loaded images or infinite scroll without explicit waits in the steps?
About qpilot on Product Hunt
“Run your manual test cases in a real browser — no code”
qpilot was submitted on Product Hunt and earned 8 upvotes and 13 comments, placing #72 on the daily leaderboard. qpilot is an open-source AI agent that runs your plain-text QA test cases in a real Chrome browser. Paste your steps → hit Run → watch pass/fail/warn per step stream live. If it hits a captcha or OTP, it pauses and asks you directly, then continues. No Playwright scripts. No selectors to maintain. Works with Claude or any OpenAI-compatible model.
qpilot was featured in Open Source (68.6k followers), Developer Tools (515.4k followers), Artificial Intelligence (473.1k followers) and GitHub (41.3k followers) on Product Hunt. Together, these topics include over 218k products, making this a competitive space to launch in.
Who hunted qpilot?
qpilot was hunted by Muhammad Mahmudov. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how qpilot stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Muhammad Mahmudov
Hey Product Hunt! 👋
I built qpilot because I was tired of watching QA teams (and myself) click through the same test cases release after release — while "proper" automation kept breaking on every UI change and needed a developer to maintain.
qpilot takes a different path: you paste your manual test case as plain text, and an AI agent opens a real Chrome browser and walks through the steps itself. You watch pass / fail / warn appear live for each step. When it hits a captcha or OTP, it doesn't die — it pauses and asks you, then continues.
What makes it different:
🧠 Reads the page like a human — via ARIA semantics, not CSS selectors, so it survives UI changes
📝 Anyone can write tests — if you can write a step-by-step description, you can automate it
⏸️ Human-in-the-loop — captchas and 2FA pause the run instead of killing it
📂 Batch mode — point it at a folder of .md test cases and run them all
🔓 Open source (MIT) — bring your own model: Claude or any OpenAI-compatible endpoint (Qwen, Ollama, vLLM)
Try it in one command:
npx qpilot
I'd love your honest feedback — especially: where would this break in YOUR testing workflow? What's the one feature that would make you actually adopt it?
GitHub: https://github.com/broxhq/qpilot