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

## About Claude Duet

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.


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

## 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](https://clip.qa/use-cases/claude-code/)


1. Copy the clip.qa report as Markdown or provide it to a coding agent with MCP or CLI support.
2. Use Claude Code as one option. Ask it to read the report, make a scoped change, run the relevant checks, and show you the diff.

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

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

## Why clip.qa for Claude Duet users

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.

## FAQ

**Q: Can Claude Duet read my clip.qa reports?**
A: 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.

**Q: Does Duet fix the bug itself?**
A: 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.

**Q: Is clip.qa affiliated with Anthropic?**
A: 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.

---

[Request beta access](https://clip.qa/apps) | [Back to clip.qa](https://clip.qa)