CoWork turns existing test cases into executable mobile automation with AI planning, human-approved replanning, and real-device execution on iOS, Android, and Flutter.
Every QA team knows what they want to test. "Log in, add an item to the cart, check the order confirmation." Saying it takes ten seconds. Then the team spends six months turning that sentence into something a machine will run: step definitions, selectors, automation glue, flaky scripts that break on every UI change.
The intent was never the hard part. The execution layer was the tax.
CoWork takes your existing natural-language or BDD test cases, converts them into structured BDD/Gherkin context, builds an execution plan, and runs the test on a real mobile device.
When the app behaves differently, like a changed label, unexpected popup, or interrupted flow, CoWork replans and asks for human approval before moving ahead. When it needs input, like an OTP, it pauses instead of guessing. If it can’t proceed, it fails honestly instead of faking a pass.
Who it’s for: QA leaders, SDETs, mobile engineering teams, and product teams with existing test cases but low execution coverage before releases.
Common use cases: Regression testing, Release readiness, checkout/login flows, OTP-heavy journeys, app flows that break often, and teams trying to reduce manual execution without rewriting everything from scratch.
What makes CoWork different is the balance: AI execution where it can move fast, human control where judgment matters.
The selector breakage problem is real.... we've seen entire automation suites go down after a single navigation update.
Curious how CoWork handles dynamic test data mid-execution. if a flow requires an OTP or an auth password during the run, can that be injected in real time or does everything need to be pre-configured before the session starts?
the six-months-to-automate part is real. my team gave up automating our iOS app last year because every release broke the selectors. went back to manual regression and shipped slower for 6 months.
what i'd want to know about qapilot: when an iOS update changes the entire navigation hierarchy, does the AI re-plan or does it break the same way our selectors did? that's the test for whether this actually saves a QA team or just shifts the breakage to a different layer.
Hey builders 👋
I am one of the makers behind CoWork!
We built CoWork - an AI agent that drives real mobile apps step by step, planning each action, reading the screen, and adapting when things go off-script.
We kept hitting the same wall: mobile automation breaks the moment a layout shifts. So we wanted something that actually sees and reasons about the screen instead of leaning on brittle scripts.
We'd love your feedback and support. Drop your thoughts/questions in the comments below and one of us will reply!
Hey folks! I’m one of the makers behind CoWork.
CoWork came out of a simple frustration: test cases are everywhere, AI is powerful but not always reliable, and humans end up double-checking everything anyway. So we thought - why not design a system where AI and humans actually CoWork (properly)?
Here’s what we built:
1. Ingest test cases from wherever you maintain them (yes, the messy reality)
2. Use AI to generate and execute, but intelligently decide when humans should step in
3. Minimize verification effort instead of pretending it doesn’t exist
We didn’t want to go all-in on rigid rules or blindly trust LLMs - CoWork is our attempt at a hybrid system that picks the right strategy at the right time.
If this sparks curiosity (or skepticism), come talk to us.
What feels useful? What feels unnecessary? Where would you not trust this yet?
Tell us where this would break in your world, and we’ll happily show you how we’re thinking about it.
Let’s CoWork on making this actually useful, not just “AI-sounding.”
Hey all ,
Excited for the launch today I am part of the team that built cowork . Would love to hear your thoughts on this .
I would be on the threads all day reading and replying to your thoughts .
Hi everyone! Aakash from QApilot here.
I'm one of the makers behind CoWork, and I'm really excited to finally share what we've been building!
CoWork helps AI and humans work together to make test automation more reliable instead of chasing full automation. We'd really appreciate your support on Product Hunt today, and I'd love to hear what you think. Thanks for checking us out!
About QApilot's CoWork on Product Hunt
“3x Mobile Automation. Same QE Team.”
QApilot's CoWork launched on Product Hunt on June 27th, 2026 and earned 0 upvotes and 9 comments, placing #22 on the daily leaderboard. CoWork turns existing test cases into executable mobile automation with AI planning, human-approved replanning, and real-device execution on iOS, Android, and Flutter.
QApilot's CoWork was featured in Developer Tools (514.7k followers) and Artificial Intelligence (472k followers) on Product Hunt. Together, these topics include over 176.2k products, making this a competitive space to launch in.
Who hunted QApilot's CoWork?
QApilot's CoWork was hunted by Rohan Chaubey. 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 QApilot's CoWork stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Rohan Chaubey
Hey everyone, Charan from QApilot here.
Every QA team knows what they want to test. "Log in, add an item to the cart, check the order confirmation." Saying it takes ten seconds. Then the team spends six months turning that sentence into something a machine will run: step definitions, selectors, automation glue, flaky scripts that break on every UI change.
The intent was never the hard part. The execution layer was the tax.
CoWork takes your existing natural-language or BDD test cases, converts them into structured BDD/Gherkin context, builds an execution plan, and runs the test on a real mobile device.
When the app behaves differently, like a changed label, unexpected popup, or interrupted flow, CoWork replans and asks for human approval before moving ahead. When it needs input, like an OTP, it pauses instead of guessing. If it can’t proceed, it fails honestly instead of faking a pass.
Who it’s for: QA leaders, SDETs, mobile engineering teams, and product teams with existing test cases but low execution coverage before releases.
Common use cases: Regression testing, Release readiness, checkout/login flows, OTP-heavy journeys, app flows that break often, and teams trying to reduce manual execution without rewriting everything from scratch.
What makes CoWork different is the balance: AI execution where it can move fast, human control where judgment matters.
If you run mobile tests, I’d genuinely love your take. Try it here: https://qapilot.io/product/cowork
Thanks for being here for the launch. I’ll be in the thread all day reading every comment.
-- Charan Tej, Product Guy @QApilot's CoWork