Design a mobile experience for developers to manage Cursor cloud agents away from their desk.

Introduction

Cursor's cloud agents (originally called background agents) run in remote machines, so a developer can hand off a task, close the laptop and come back to a finished branch. With Cursor 3's Agents Window, many developers now run several agents in parallel across local worktrees and the cloud. That creates a new job: supervising agents when you are not at your desk. An agent may finish, get stuck waiting for input, fail its tests or open a pull request while you are on a train or in a meeting.

This question asks us to design a mobile experience for that job. I'll clarify scope, explain why it matters, pick a user segment, map pain points, design a solution and define metrics.

Step 1

Clarify Questions (3 minutes)

• Is this a native iOS and Android app, or an improvement to Cursor's existing mobile web access to agents? I'll assume a dedicated mobile experience (native app or installable web app) that connects to the same cloud agents used from the desktop and web.

• Should users be able to start new agents from mobile, or only monitor and approve? I'll include both, but the core job is supervision.

• Are we designing for individuals on Pro and Ultra plans or for teams? I'll design for individual developers first, with team controls respected (for example, branch protection and admin policies).

• Any security constraints? I'll assume enterprise admins can restrict mobile merges and that all actions follow the repository's existing permissions.

Propose the Goal

Let developers keep cloud agents moving when they are away from their desk, so less agent time is wasted waiting on a human, without lowering code quality or security.

Define the Scope

In scope: notifications, agent status, reviewing summaries and diffs, replying to agents, approving pull requests within policy, starting simple tasks. Out of scope: full code editing on a phone.