Guides published jul 5, 2026
In this guide, you will learn how to screenshot a bug on your website from your phone, send it to a Cursor Cloud agent, and review the resulting pull request in GitHub before you make it back to your desk. The new Cursor mobile app might be the best way to maintain codebases on the go when the issue is visible, scoped, and ready for a quick agent pass.
You will set up a mobile bug-fix loop: screenshot the issue, start a Cursor Mobile thread on the right repo, attach the screenshot, ask for a small fix, and review the PR from GitHub Mobile.
By the end, you should have a repeatable workflow for turning mobile QA moments into GitHub pull requests with changed files, validation notes, and a clear review path.
On desktop, enable Remote Agents so Cursor can work on your machine and prep local changes before you get back to your desk. That is useful when a mobile bug report turns into a deeper fix that needs your local environment, existing branches, or desktop-only testing.
You can also turn the prompt into a reusable incident template:
Investigate this bug on [page or route]. Use the attached screenshot and note to find the relevant component, make the smallest safe fix, and open a PR. Include changed files, validation notes, and anything I should review before merging.Use that template for support tickets, QA screenshots, and urgent UI regressions. Keep the task small, keep the screenshot clean, and use GitHub review as the checkpoint before anything ships.
For more context on the mobile release, Cursor's official iOS launch post (https://cursor.com/blog/ios-mobile-app) and launch thread (https://x.com/cursor_ai/status/2071641103191998810) show how Cursor expects people to start agents, track work, and move PRs forward from a phone.
Start by installing the official Cursor iOS app from Anysphere (https://apps.apple.com/us/app/cursor/id6767085653). Cursor's iOS launch post (https://cursor.com/blog/ios-mobile-app) describes the app as a way to start agents from your phone, track work, review artifacts, and move PRs forward while you are away from your computer.
You will also want GitHub Mobile (https://apps.apple.com/us/app/github/id1477376905). Cursor can create and update the PR, but GitHub is where you will review the diff, approve it, merge it, or leave follow-up comments from your phone.
Pro tip: Use the Anysphere App Store link above. There are fake Cursor apps in the App Store, and grabbing the wrong one will break the workflow before you even get to the repo.
You also need a Cursor Pro plan for this workflow. Get that handled before you try to start a mobile agent so you are not troubleshooting plan access in the middle of a bug report.
Open the website or app screen you are working on from your phone. Then take a screenshot of the bug, broken layout, or UI change you want fixed.
The screenshot should show the problem clearly. If the issue is a broken CTA, bad spacing, hidden button, weird modal, or mobile layout regression, keep the important area visible. If the screenshot includes private customer data, tokens, internal URLs, or anything sensitive, clean it up before sending it to the agent.
Add a short note with the page, feature, or route and the expected behavior. Keep it plain:
Page: [page or route]
Issue: [what is visibly broken]
Expected: [what should happen instead]
Context: attached screenshot from my phonePro tip: Cursor Mobile works best when the bug is visible and scoped. Save broad redesigns, security-sensitive changes, unclear repro steps, and heavy local debugging for desktop.
Open Cursor Mobile and go to the workspace or repo list. Choose the repo that owns the page you just screenshotted.
If you are using All Repos, pick the correct project before you start the agent. This is a small step, but it prevents the agent from wasting time in the wrong codebase.
Tap the plus button to start a new thread. Attach the screenshot before you send the prompt so the agent has visual context from the beginning.
Use a short prompt that names the target page and asks for the smallest useful fix:
Investigate this bug on [page or route]. Use the attached screenshot, find the relevant component, make the smallest safe fix, and open a PR.If you know the likely file, component, or recent change, add one short sentence after the prompt. Do not turn the phone prompt into a full spec. The goal is to give the agent enough context to start, then let the PR and validation notes carry the details.
After the task starts, Cursor will show progress in the mobile thread. You can leave the app and come back when the agent needs input or finishes.
When the agent returns, look for evidence before you approve anything. A useful result should include the changed files, a root-cause summary, validation notes, and a PR you can inspect. Screenshots, logs, preview links, or test output are even better.
If the agent says the bug is fixed but gives no evidence, ask for a tighter summary before reviewing the PR:
Before I review this, summarize the files changed, why those files were chosen, how you validated the fix, and what I should check first in GitHub.This keeps the mobile workflow useful without turning it into blind trust. The phone is great for starting the fix and triaging the result. The PR still deserves a real review.
Cursor will send you a notification when the work is ready. Tap through to the PR and review it in GitHub Mobile.
Start with the file list and diff. Confirm the change is scoped to the bug you reported, then check the validation notes from the Cursor thread. If the fix is clean, approve and merge it from GitHub. If it is close but needs edits, leave a PR comment and tag @Codex with the exact change you want.
Good follow-up comments are specific:
@Codex tighten the mobile spacing only on the checkout CTA. Do not change the desktop layout. Add a short note explaining how you verified the mobile view.Save the Cursor thread, PR link, screenshot, and final summary if this is part of a customer issue or incident. That gives you a clean audit trail when you are back at your desk.
Keep going
Members get all guides, courses, live sessions, and $1,000+ in partner perks.