clip.qa is a mobile app that turns screen recordings into structured bug reports. Record a bug on your phone, and clip.qa's AI drafts a report with steps to reproduce and device context for you to review. Reports export as markdown for AI coding tools like Claude Code and Cursor, or to paste into any tracker. Jira, Linear, Slack, GitHub Issues and Notion integrations are coming soon. No SDK required in the app you test.

What is Vibe QA — and why does it matter?

Vibe QA is quality assurance for apps built with AI coding tools — a practice that emerged alongside vibe coding (using AI assistants like Claude Code, Cursor, and Copilot to build apps rapidly). Because vibe-coded apps ship faster than traditional QA can keep up, Vibe QA uses AI-native tools to close the loop: capture bugs visually, generate LLM-ready reports automatically, and feed them back to the same AI tools that built the app. clip.qa is built for Vibe QA.

Does clip.qa work with OpenClaw projects?

Yes. clip.qa produces a structured report your agent, including OpenClaw, can read through MCP or a pasted prompt.

How is clip.qa different from Jam?

Jam has a Chrome extension, a Mac app and an iOS app, plus AI summaries and an MCP server. No Android app is documented. clip.qa records on iOS, Android and in Chrome (beta, request access), with no SDK in the app you test. clip.qa's MCP also records each fix attempt (pending, succeeded, failed) with its commit or PR, and can diff reports.

Do I need to install an SDK or add code to my app?

No. clip.qa works without any SDK integration. It uses your phone's native screen recording, so it works on any app — including competitor apps you're testing, OpenClaw projects, and apps you don't have source access to (subject to OS limits such as FLAG_SECURE).

How much does clip.qa cost?

Free: 30 bug reports and 30 AI-assisted reports a month. Team ($12.99/mo or $129/yr, billed per creator seat, viewers free): unlimited bug reports, 200 AI-assisted reports and 50 share links a month. Enterprise pricing is custom; confirm current quotas and features with sales. Audit logs and priority support are listed; SAML/SSO is coming soon.

What platforms does clip.qa support?

The clip.qa web dashboard is available now; the iOS app, Android app and Chrome extension are in beta (request access at hello@clip.qa). Bug reports can be copied as markdown into any tracker (Jira, Linear, GitHub Issues; native integrations coming soon) or used directly as prompts for Claude, Cursor, and other AI coding tools.

Claude Duet

clip.qa / Use cases / Claude Duet

clip.qa for Claude Duet: send bug reports your agent can fix

Duet works in the background and checks with you before it acts. For a bug recorded in clip.qa, use Claude Code or another MCP- or CLI-capable agent to read the report and attempt the fix.

The clip.qa iOS app, Android app and Chrome extension are in beta. Request access on the apps page.

Request beta access See all integrations

The agent

About Claude Duet from Anthropic

Anthropic announced Claude Duet on October 21, 2026 as a research preview, available by waitlist to US Pro, Max and Ultra subscribers. It is a proactive agent app: it gives you a morning brief, takes on tasks, keeps working while you are away and checks with you before acting. It is powered by Claude Opus 5.5, works with more than 6,000 connectors and plugins, and runs on iOS, Android and claude.ai. It is built for professionals and small business owners.

How it works

From a bug on your phone to a coding-agent fix attempt

1. Record the bug on your own device

Use the clip.qa iOS or Android app (beta, request access), or the Chrome extension (beta, request access), to screen-record the bug. No SDK goes into the app you test.

2. Review the AI draft

clip.qa turns the recording into a report: title, severity, kind, suspected root cause, steps to reproduce, and expected vs actual behavior when the recording shows a defect, plus key-moment screenshots and device context (OS, device, memory, thermal). It is a draft, so check it before you hand it to your coding agent.

3. Use a coding agent with the report

Duet's documentation does not yet show custom connectors. Use Claude Code or another MCP- or CLI-capable agent to read the clip.qa report and fix the bug.

4. Review the coding agent's diff

Check the changed files and test results before you accept the fix. Keep any action that affects production under your own review.

Hand off the report

Give the report to a coding agent

Duet is a research preview on a waitlist, so access and features can change. Its documentation does not yet show custom MCP connectors. Use a coding agent with MCP or CLI access to read the report and work on the bug.

Use Claude Code with clip.qa reports

1Copy the clip.qa report as Markdown or provide it to a coding agent with MCP or CLI support.

2Use Claude Code as one option. Ask it to read the report, make a scoped change, run the relevant checks, and show you the diff.

Honest fit

Choose Duet on its own if

You want a morning brief for your wider work, not for bug intake.
The task is not about a defect on a device.
You do not need a coding agent in the loop.

Duet works with connectors and plugins, but its documentation does not yet show a custom MCP path for clip.qa. A coding agent such as Claude Code can read the report through MCP or CLI access and attempt the fix. For solo developers and small teams shipping mobile apps, the recording becomes the report.

clip.qa and Claude Duet FAQ

Can Claude Duet read my clip.qa reports?

Duet's documentation does not yet show custom MCP connectors. Use Claude Code or another MCP- or CLI-capable agent to read the clip.qa report. Duet is a research preview on a waitlist, so check Anthropic's current availability.

Does Duet fix the bug itself?

Duet can take on tasks, but its documentation does not yet show custom MCP connectors for clip.qa. For this workflow, use Claude Code or another MCP- or CLI-capable agent to read the report and attempt the code change, then review the result.

Is clip.qa affiliated with Anthropic?

No. clip.qa is an independent product with no partnership with Anthropic. Anthropic's current Duet documentation does not show a custom clip.qa connector.

Your coding agent attempts the fix. clip.qa captures the bug.

Record the bug, review the AI draft, then send it to your agent. Free plan available.

Request beta access See all integrations