Cursor iPad Inbox: Close the Agent PR Loop Away From Your Desk

While cloud agents open pull requests, the scarce resource is no longer “hands on a keyboard.” It is a human who can decide whether a change is safe to merge. Cursor’s July 29, 2026 release — iPad on all paid plans, plus Inbox and a full PR review surface on iPhone and iPad — is aimed at that bottleneck.

Core takeaway: Cursor mobile is not a miniature IDE. It is the human gate for reviewing, approving, and merging agent output.

Why it matters

Mature agent workflows are asynchronous. You can close the laptop while a cloud VM keeps testing, attaching demos/logs, and opening PRs. Team throughput then depends less on how fast agents type and more on how quickly — and safely — humans close the review loop.

The Jul 29 update centers on three surfaces:

1. Inbox — see in-progress agents, items that need your attention, and PRs already in review.
2. Full PR review — comments, checks, and approvals on mobile; add or change reviewers; prompt the agent to resolve review comments.
3. iPad layout — pin multiple sidebar chats, keep a review open beside chat, and read file diffs at a usable size.

Bitbucket and Azure DevOps SCM support, multi-PR sessions (open every PR a chat created, not only the last), and in-app team switching round out the release. The product message — close the agent loop from anywhere — now has concrete UI.

How it compares

The useful contrast is not “coding on a phone.” Cursor’s own help docs frame the app as directing and reviewing agents. When you need to edit, return to desktop or the web Agents UI. Blurring that line creates false expectations (“I’ll refactor on the train”) and worse review quality.

The June 29 iOS app opened cloud-agent launch, Live Activities, push notifications, and merge-from-phone. July 29 upgrades the review surface to full PR depth and makes iPad a first-class device. This is also distinct from multiplayer “Conductor-style” collaboration: today is about the solo, away-from-desk human approval gate.

Code / config example

Share a lightweight “mobile merge gate” contract in the repo so agents and reviewers use the same bar:

# .cursor/mobile-merge-gate.yaml
# Human gate for cloud-agent PRs reviewed on Cursor iOS/iPad
version: 1
when: before_merge_from_mobile
require:
  checks: green_or_explicitly_waived
  diff_scope: "single concern; no drive-by refactors"
  secrets: "no new env keys or tokens in diff"
  migrations: "forward-only; rollback note in PR body"
  artifacts: "demo/screenshot/log reviewed when agent attached them"
ask_agent_to_fix_if:
  - "CI failed on a flake you cannot reproduce on mobile"
  - "review comment needs a code change larger than a one-liner"
never_merge_on_mobile_if:
  - "auth, billing, or data-deletion paths changed"
  - "you cannot see the full diff (too large) without desktop"

This is an ops contract, not clever code. The mobile merge risk is not typo rate — it is judgment error when a small screen makes a wide diff look “probably fine.”

Practical use

Keep the loop boring and repeatable:

1. Send long work to a cloud agent from desktop/web so it continues after the laptop closes.
2. Open Inbox when notified. Triage into in-progress / needs attention / PR review first.
3. Artifacts → diff → checks → comments. If the agent attached a demo, screenshot, or log, use it to test the claim before drowning in hunks.
4. Re-prompt the agent for small, crisp fixes; bounce structural changes to desktop.
5. Merge only when the gate passes. Otherwise leave a one-line blocked reason in Inbox.

The first week I used Inbox, I almost built a bad habit: notification → merge. One green-CI PR still hid an unintended config-file change that was easy to miss on a phone screen. After that, never_merge_on_mobile_if became the first checklist I read.

Teams on Bitbucket or Azure DevOps also get a more realistic mobile path after Jul 29 — GitHub is no longer an implicit prerequisite for the agent merge loop. And when one chat opens multiple PRs, multi-PR sessions mean you should open all of them before calling the job done.

Senior-engineer perspective

In an agent-heavy org, seniors design quality gates, not faster keystrokes. Mobile Inbox puts that gate in your pocket. Without written criteria, Inbox is just notification spam with a prettier badge.

Suggested team rules:

• Document what is allowed to merge on mobile (the YAML above is enough to start).
• Require desktop review + a second reviewer for high-risk paths.
• Template agent re-prompt language (“Fix only this comment with minimal diff. No drive-by refactors.”).
• Set an Inbox triage SLA (e.g., classify needs attention within four hours — classify, not necessarily merge).

Full PR review on mobile also does not mean architecture debates should end in a phone thread. Prefer an issue/RFC for design decisions; use mobile comments for concrete, bounded fixes.

Using it in Cursor

A concrete practice path:

1. Install/sign in to the Cursor iOS/iPad app on a paid plan (complete org SSO on the web first if required).
2. Start a cloud agent from the desktop Agents Window (or hand off via Remote Control) and confirm the same session appears on the phone.
3. On a Jul 29+ build, open Inbox and deliberately create a “needs attention” item with an ambiguous follow-up.
4. Exercise PR review once: checks, comments, reviewer changes. If you use Bitbucket/ADO, verify SCM connectivity first.
5. Use a throwaway branch where one chat opens two PRs and practice multi-PR session navigation.
6. Share the mobile merge-gate YAML with the team and collect only violations for a week, then tighten the rules.

If you need to edit, leave mobile on purpose. “Continue on desktop” is the correct escape hatch.

FAQ

Can I edit code directly in the Cursor mobile app?

Not according to official help. The app focuses on directing agents, reviewing diffs/artifacts, and merging PRs. There is no editor, terminal, or file browser.

How is Inbox different from a plain agent list?

Inbox prioritizes the human queue: in-progress work, items that need your attention, and PRs in review. It is closer to operating a gate than browsing sessions.

Is iPad just a bigger iPhone UI?

As of Jul 29, the iPad layout is rebuilt for the extra space: pinned sidebar chats, split review + chat, and fuller diffs. Treat it as a review workstation, not a scaled phone skin.

Is GitHub required?

No. The Jul 29 changelog calls out Bitbucket and Azure DevOps SCM support, so the mobile review loop is not GitHub-only.

Should every PR merge from mobile?

No. Auth, billing, data-deletion, and large migrations still deserve desktop diff review and local verification. Mobile shines for narrow, green-check agent PRs.

Sources

• Cursor, now on iPad (Changelog, 2026-07-29)
• Cursor Changelog index
• Build from anywhere with Cursor for iOS
• Cursor for iOS help
• Cursor Mobile App for iOS (Changelog)

Conclusion

The more agents write code, the more engineering value concentrates in disciplined approval. Cursor’s iPad app, Inbox, and full PR review move that approval off the desk — while still drawing a clear product line: mobile is not the editor. Looking ahead, teams may compete less on how many agents they launch and more on how cleanly they empty Inbox without lowering the merge bar.