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.

clip.qa / Use cases / Goose

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

Goose installs, runs, edits and tests code on your machine, with the model you choose. clip.qa gives it a report written from a recording of the bug on your phone.

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 Goose by Block

Goose is an open-source (Apache-2.0) agent from Block, available as a CLI and a desktop app. It adds abilities through MCP-based extensions, over stdio and Streamable HTTP, and its developer extension runs commands. Its README says it can install, execute, edit and test with any LLM.

Read the Goose bug-report workflow

How it works

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

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

3. Add clip.qa as a Goose extension

Add the clip.qa MCP server as an extension in Goose, then ask it for the latest report. Or paste the Markdown report into a session.

4. Review what Goose changes

Goose gets the steps and context it needs to attempt a fix and test it. You review the diff before you keep it.

Connect Goose

Add clip.qa to Goose

Goose extensions are MCP servers, and it accepts both local processes and Streamable HTTP. Follow the Goose extensions guide for the exact steps. Block 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 a Streamable HTTP extension that points at https://mcp.clip.qa/mcp, or a local extension that runs the package @clip-qa/mcp-server with your clip.qa API key.

2Goose runs commands through its developer extension, so the clip.qa CLI (npm @clip-qa/cli) is another route.

3Or paste the Markdown report into a Goose session with no setup.

Honest fit

Choose Goose on its own if

You want a local agent that works with any model you pick.
The task is code you can describe, not a bug you saw on a device.
You want a desktop app and a CLI for the same agent.

Goose gives you freedom over the model and the tools. clip.qa gives that freedom something concrete to work on. For a solo developer or a small team, one recording replaces the paragraph of steps you would otherwise type.

clip.qa and Goose FAQ

How do I add clip.qa to Goose?

Add it as an MCP extension: Streamable HTTP at https://mcp.clip.qa/mcp, or a local process running @clip-qa/mcp-server with your API key. The Goose extensions guide covers the steps. You can also paste the Markdown report.

Does Goose fix the bug on its own?

Goose gets the steps, screenshots and device context it needs to attempt a fix. It will not solve every bug, so run the tests and read the diff.

Is clip.qa made by Block?

No. clip.qa is independent of Block, with no partnership. Goose supports MCP, and that standard protocol is the connection.

Goose runs the fix. clip.qa shows it the bug.

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

Request beta access See all integrations