PocketQA

Your agent builds it.Your phones test it.PocketQA discovers it.

Your first test

How it works

Your devices, your agent, your network. Four steps to your first test.

1

Connect your agent

  • Claude Code
  • Cline
  • Junie
  • Warp
  • Mistral Le Chat
  • Cursor
  • Roo Code
  • Amp
  • Factory Droid
  • Microsoft Copilot Studio
  • OpenAI Codex
  • Kilo Code
  • opencode
  • Augment Code
  • Lovable
  • GitHub Copilot
  • Continue
  • Goose
  • Devin
  • v0
  • Windsurf
  • Zed
  • Kiro
  • Claude
  • Replit Agent
  • Gemini CLI
  • JetBrains AI Assistant
  • Amazon Q Developer CLI
  • ChatGPT
  • Bolt
Your coding agent
Set up PocketQA so you can test my site on real phones and browsers:
1. Add the MCP server https://staging.pocketqa.dev/mcp (remote, over HTTP). Sign in with GitHub when it asks.
2. Add this rule to this project’s instructions (CLAUDE.md, AGENTS.md or your rules file): “Before saying a web change is done, test it with PocketQA on real phones, and fix what it finds.”
3. Then test my site with PocketQA and tell me what it found.
2

Add your site

PocketQA navigates your site, tells your agent what broke and how to fix it.

PocketQA never sees your source code.

Free while in early access. No credit card.

3

Install PocketQA

4

Connect your phone

Your phone. Your test lab.

my-site.com

New button added ↓

PocketQA is testing this button

Buy
404

Page not found

Buy opened a missing page.

✓ Ready to ship!

Checkout works. The fix passed on the same devices.

PocketQA: 3 passing checks PocketQA3 passing checks
✓ Buy works. Fix checked.

Keep the loop moving

Less time testing.
More time building.

Get from a code change to a tested fix without managing every step yourself.

01 / Speed

Get feedback while you build.

Your agent can run a check, act on the result and test the fix in the same workflow.

02 / Token efficiency

Give your agent the useful context.

A focused result: what broke, where and what to try. Grouped issues keep repeated failures from becoming repeated investigations.

03 / Testing knowledge

Put testing expertise in the loop.

Device checks and failure diagnosis help your agent distinguish a broken feature from a lab problem.

Built to grow with you

Start with one phone.
Grow with your product.

Keep the workflow. Add devices, sites and teammates as you need them.

Start

Your first project.

Use the Mac and phone you already own.

Expand

More coverage.

Add the browsers and devices your customers use.

Collaborate

Your team’s test lab.

Bring teammates and client sites into the same workflow.

Your devices. PocketQA’s testing knowledge.

You bring the hardware. PocketQA brings the checks, diagnosis and feedback your agent uses to fix problems.

Keep a record of what was fixed

Reports log the failure and its retest. Share them with your team or clients when you need the evidence.

Example report

Buy opens a missing page

Example flow: tap Buy · Before the fix

1 issue found
First test
DeviceBrowserResult
iPhoneSafari404 — not found
AndroidChrome404 — not found
DesktopChrome404 — not found

What your agent receives

Buy opens a page that returns 404.

What happened
The test taps Buy. The next page returns 404 (not found).
What should happen
Buy opens the checkout page.
Suggested fix
Check the Buy link and make sure its destination exists, then test again.
Fix checked

Checked on the same devices. Buy opens checkout. The test passes after the fix.

PocketQA: passing on 4 devices PocketQApassing on 4 devices

Build with us

Your next release starts here.

Early access

Your devices.
Your lab. Free.

Put the computers and phones you already own to work.

  • No limit on computers or phones
  • Your coding agent, your workflow
  • No credit card required
Start testing free →

Free throughout early access. Setup, device support and test accuracy are still improving; some tests may return incomplete results.

What PocketQA sends and keeps

Customer suggestions

What should we
build next?

A missing integration? A smoother setup? A test you wish you could run? Tell us what would make your lab more useful.

Send a suggestion to our private issue tracker. Sign in to PocketQA.

Before you plug in

A few things worth knowing.

What do I need?

A Mac (Intel or Apple silicon) you can leave plugged in, and the phones you already have: an iPhone and an Android phone are a good start. A spare laptop works well.

Does my code leave my computer?

No. PocketQA only asks who you are, and only results leave your lab: which device, passed or failed, timings and the page's own errors. Step screenshots stay on your lab unless your team switches them on.

How is this different from a device cloud?

You test on the devices on your desk, as often as you like. It’s free during early access. Device clouds charge by the device or the minute. More device options may come later.

Which agents work with it?

Anything that speaks MCP (Claude Code, Claude, Cursor and others), plus scripts and CI through a token.

Put your next change to the test.

Start with the phones you already have. Free during early access.

Build your device lab →