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.

Hermes Agent

clip.qa / Use cases / Hermes Agent

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

Hermes Agent runs in your own environment and connects to the tools you give it. clip.qa gives it the one thing it cannot see: what the bug looked like on a real 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 Hermes Agent by Nous Research

Hermes Agent is an open-source (MIT) agent from Nous Research. It runs shell commands through six terminal backends (local, Docker, SSH, Modal, Daytona and Vercel Sandbox) and connects to external MCP servers, as its MCP Integration doc describes. It also reaches you through messaging gateways such as Telegram, Discord and Slack.

How it works

From a bug on your phone to a fix attempt in Hermes Agent

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 Hermes Agent.

3. Connect clip.qa as an MCP server

Hermes Agent documents external MCP support. Test the clip.qa transport, authentication and retrieval of a real report before relying on this path. Otherwise, paste the Markdown report into a chat.

4. Let it attempt the fix, then review

Hermes Agent gets the steps, screenshots and context it needs to attempt a fix in its backend. You review the result before anything ships.

Connect Hermes Agent

Give Hermes Agent a clip.qa report

Hermes Agent's MCP Integration doc covers external servers and supported transports. It does not verify this clip.qa connection: test the configured transport and authentication by retrieving a real report. Nous Research 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

1Use the Hermes Agent MCP Integration instructions to configure https://mcp.clip.qa/mcp or the local package @clip-qa/mcp-server with your clip.qa credentials, then test authenticated retrieval of a real report.

2Hermes Agent runs shell commands, so you can also test the clip.qa CLI (npm @clip-qa/cli) in its documented environment.

3Or send the Markdown report straight into a Hermes Agent conversation.

Honest fit

Choose Hermes Agent on its own if

You want an agent that lives on a server and talks to you in your chat apps.
The work is automation or research, not a bug you saw on a device.
You already have a written, reproducible report.

Hermes Agent is strong at running things and staying reachable. It has no eyes on your phone. clip.qa records the bug on the device and writes it up, so a solo developer shipping a mobile app can hand the agent a report instead of a vague message.

clip.qa and Hermes Agent FAQ

Does Hermes Agent work with clip.qa?

Hermes Agent documents remote HTTP and local stdio MCP connections, including OAuth for remote servers. The clip.qa server has not been verified with Hermes: test successful retrieval of a real report using https://mcp.clip.qa/mcp or @clip-qa/mcp-server. Pasting the Markdown report works with no setup.

Can Hermes Agent fix every bug from a clip.qa report?

No. It gets the steps, screenshots and device context it needs to attempt the fix. Complex bugs still need your judgment, and you should review every change.

Is this made with Nous Research?

No. clip.qa is independent of Nous Research and Hermes Agent. There is no partnership; the connection relies on standard MCP.

Hermes Agent does the work. 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