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.

Devin

clip.qa / Use cases / Devin

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

Devin takes tickets and opens pull requests. clip.qa turns a screen recording into a ticket-ready report, so Devin starts from what actually happened on the device.

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 Devin by Cognition

Devin is Cognition's software engineering agent. Its site describes it writing and testing code, opening pull requests and fixing failed CI. Devin takes work from Slack and Teams, from Linear and Jira tickets, and from GitHub. Its docs list MCP support over remote HTTP and local servers.

Read the Devin bug-report workflow

How it works

From a bug on your phone to a fix attempt in Devin

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 Devin.

3. Get the report to Devin

Connect the clip.qa MCP server to Devin, or copy the report as Markdown and paste it into a Devin session or into the ticket you assign to Devin.

4. Review the pull request

Devin gets the steps, screenshots and device context it needs to attempt a fix and open a PR. You review it. Over MCP, your agent can log the attempt with its commit or PR.

Connect Devin

Three ways to get a clip.qa report to Devin

Native clip.qa integrations for Jira, Linear, Slack, GitHub Issues and Notion are coming soon. Until then, use MCP or paste the report. Cognition did not build this connection.

clip.qa connection details

Remote MCP server:  https://mcp.clip.qa/mcp
Local MCP server:   npm @clip-qa/mcp-server
CLI:                npm @clip-qa/cli

1Add clip.qa as an MCP server in Devin's MCP settings: the remote endpoint https://mcp.clip.qa/mcp, or the local package @clip-qa/mcp-server with your clip.qa API key. See the MCP page in the Devin docs.

2Paste the Markdown report into a Devin session in Slack, Teams or the Devin app.

3Paste the Markdown report into a Linear or Jira ticket and assign it to Devin.

Honest fit

Choose Devin on its own if

The task is a backlog item or a failing CI run, not a device bug.
Your team already routes work to Devin through tickets and Slack.
You want an agent to own a task end to end in its own environment.

Devin is built for teams with a ticket queue. clip.qa fills that queue for a solo developer or a small team: you record the bug on your phone and get a ticket-ready report, without writing it up by hand.

clip.qa and Devin FAQ

How do I send a clip.qa report to Devin?

Connect the MCP server (https://mcp.clip.qa/mcp or @clip-qa/mcp-server) in Devin's MCP settings, or paste the Markdown report into a session or ticket. Native Jira and Linear integrations from clip.qa are coming soon.

Will Devin fix the bug?

Devin gets the steps, logs and screenshots it needs to attempt a fix and open a pull request. It will not fix every bug, so review the PR before you merge.

Does Cognition endorse clip.qa?

No. clip.qa is an independent product with no partnership with Cognition. Devin supports MCP, and that standard protocol is the connection.

Devin opens the PR. clip.qa writes the ticket.

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

Request beta access See all integrations