Choose an agent
Control Cursor Cloud agents from Android
Cursor Cloud is the path for work that can continue without the paired computer online. FireCursor can expose cloud runs, artifacts, usage, pools, machines, and pull-request context under the connected Cursor account.
Quick answer
The shortest useful version.
Configure the Cursor Cloud account path, choose a bounded cloud-safe task, confirm the target repository and machine context, then monitor status and artifacts from Android until you can review the result.
Step by step
Do this with confidence.
- 01
Confirm the cloud boundary
Cursor Cloud runs in Cursor’s environment under the connected Cursor account. Decide whether the repository and task are appropriate for that boundary.
- 02
Choose the target
Verify the repository, source ref, machine or pool context, and task before launch.
- 03
Monitor the run
Use Android to follow status, inspect artifacts and observed usage, steer when supported, or cancel a run that has drifted.
- 04
Review the delivery surface
Inspect the resulting branch or pull-request context and run your normal repository checks before merge.
Local and cloud are deliberately different
A local FireCursor run keeps execution on the paired computer. A Cursor Cloud run continues in Cursor’s cloud. The mobile interface can unify supervision, but it should never blur those execution and data boundaries.
Use the Cloud path for availability, not by default. Sensitive local-only work should remain on the paired machine.
Cloud run checklist
- Repository and branch are correct
- Task contains no unnecessary secrets
- Machine or pool selection is understood
- Stop conditions are explicit
- Artifacts and pull-request output will receive normal human review