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).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
rea-captcha
Safe CAPTCHA handoff for Browser Use agents
rea-captcha keeps Browser Use and Playwright jobs in the same browser session when a verification page interrupts the run. It detects the gate, pauses for an authorized test action or bounded human handoff, and resumes only after fresh evidence shows the current challenge cleared. It ships as a local MCP server and TypeScript SDK, with recorded reCAPTCHA, Turnstile, hCaptcha test-key demos plus an owned image/text case. It is not a production CAPTCHA bypass.
Hey Product Hunt — I built rea-captcha after watching browser agents get most of the way through a task, hit a verification page, and lose the session.
The awkward part was not detecting a CAPTCHA. It was deciding when the agent could safely continue. A click is not proof that the protected page accepted the verification, and a late success from an older attempt should not release a newer gate.
rea-captcha keeps the existing Playwright/CDP page, pauses for either an authorized test action or a bounded human handoff, then checks fresh page evidence before resuming. The live demo uses official non-production keys for reCAPTCHA, Turnstile, and hCaptcha, plus one owned image/text case. Unknown production challenges stop for the user; this is not a generic bypass.
I’d especially value feedback from people building with Browser Use: what should count as a safe resume signal in your workflow?
About rea-captcha on Product Hunt
“Safe CAPTCHA handoff for Browser Use agents”
rea-captcha was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #277 on the daily leaderboard. rea-captcha keeps Browser Use and Playwright jobs in the same browser session when a verification page interrupts the run. It detects the gate, pauses for an authorized test action or bounded human handoff, and resumes only after fresh evidence shows the current challenge cleared. It ships as a local MCP server and TypeScript SDK, with recorded reCAPTCHA, Turnstile, hCaptcha test-key demos plus an owned image/text case. It is not a production CAPTCHA bypass.
On the analytics side, rea-captcha competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how rea-captcha performed against the three products that launched closest to it on the same day.
Who hunted rea-captcha?
rea-captcha was hunted by Asklv. 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.
For a complete overview of rea-captcha including community comment highlights and product details, visit the product overview.
Asklv