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

Jules works from GitHub. clip.qa turns the bug you saw on your phone into a report you paste into a GitHub issue, so Jules starts from the real steps instead of a one-line guess.

## About Jules

Jules is Google's coding agent. It clones your repository into a cloud VM, plans the change and opens a pull request. Its site describes picking up a GitHub issue that carries the jules label, or a prompt typed on the web. Daily task limits depend on your Jules plan.


[Read the Jules bug-report workflow](https://clip.qa/blog/google-jules-shutdown-bug-reports/)

## How it works

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

### 3. Open a GitHub issue with the report
Copy the report as Markdown and paste it into a new issue in your repo. Add the jules label so Jules picks it up. A native GitHub Issues integration from clip.qa is coming soon, so for now this step is manual.

### 4. Review the pull request
Jules gets the steps and context it needs to attempt a fix and opens a PR. You review it before it merges.

## Send a clip.qa report to Jules through GitHub

Jules documents GitHub issues and web prompts as the ways to give it work, so this page uses the GitHub path. Google did not build this connection.



1. In clip.qa, copy the finished report as Markdown.
2. In your GitHub repo, open a new issue and paste the report as the body.
3. Add the jules label, or paste the same text into a Jules task on the web.

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

## Choose Jules on its own if

- Your repo is on GitHub and the task is clear from the issue text alone.
- You want an agent that works in a cloud VM while you do something else.
- The fix does not depend on seeing how the app behaved on a device.

## Why clip.qa for Jules users

A GitHub issue titled 'login broken on iPhone' gives Jules little to work with. A clip.qa report gives it steps, expected vs actual behavior and device context taken from the recording. That matters most for solo developers shipping AI-built mobile apps, who rarely have time to write good issues.

## FAQ

**Q: Does clip.qa connect to Jules directly?**
A: Not directly. Jules takes GitHub issues with the jules label, so you paste the clip.qa Markdown report into an issue. A native GitHub Issues integration from clip.qa is coming soon.

**Q: Can Jules watch the recording?**
A: Jules works from the text of the issue. The report carries steps, expected vs actual behavior and device context from the recording. You can add a clip.qa share link for human reviewers.

**Q: Is this a Google integration?**
A: No. clip.qa is independent of Google. Nothing here was built by Google. It uses the GitHub issue flow that Jules documents.

---

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