Guide
How to use Cursor from your phone
Cursor has an iOS app and an Android PWA for Cloud Agents. Other mobile clients can connect you to Cursor on your computer. Compare where each option runs and what it means for your workflow.
Reviewed August 26, 2026. Sources: Cursor mobile docs · Cursor pricing
Ways to use Cursor from your phone
Option 1
Cursor for iOS and Android PWA
How it works Cursor’s iOS app runs Cloud Agents and, on supported paid plans, Remote Control for a Git-backed workspace on your computer. Android uses the cursor.com/agents PWA for Cloud Agents; there is no native Android app.
Trade-off Cloud Agents run in Cursor infrastructure; Remote Control has plan, Git, and awake-host requirements.
Best for Cursor users who want the official experience and are comfortable with Cursor Cloud Agents.
Visit Cursor for iOS and Android PWA → Compare with Sesori →Option 2
Paseo
How it works Paseo is an open-source orchestrator with iOS, Android, desktop, web, and CLI clients. It runs Cursor CLI locally alongside 38 other documented agents and can connect directly or through an encrypted relay.
Trade-off It is a broad orchestrator, so it is less focused on a single mobile workflow.
Best for Developers who want broad open-source agent coverage, self-hosting options, and several client surfaces.
Visit Paseo →Option 3
Orca
How it works Orca is an MIT-licensed development environment for Cursor CLI and other terminal agents in isolated worktrees. Its iOS and Android companion pairs with Orca desktop for status, replies, file browsing, review, and commits.
Trade-off The desktop remains the source of truth and must stay reachable.
Best for Developers who want a desktop-first worktree IDE with a capable phone companion.
Visit Orca →Option 4
T3 Code
How it works T3 Code is an MIT-licensed desktop and web control plane with iOS and Android companions. It runs the opt-in Cursor CLI on its host and supports LAN, Tailscale, SSH, custom HTTPS, or T3 Connect.
Trade-off You choose and configure the remote-connection approach.
Best for Developers who want a forkable desktop control plane and multiple remote-connection choices.
Visit T3 Code →Option 5
CodeAgent Mobile
How it works CodeAgent Mobile offers iOS, Android, and web access through IDE plugins and a CLI. It lists Cursor among its supported coding tools.
Trade-off Prompts and output pass through its backend relay, so review its current architecture and plan limits.
Best for Teams already using its supported IDE plugins or developers prioritizing integration breadth.
Visit CodeAgent Mobile →Option 6
Sesori
How it works Sesori connects iOS and Android to Cursor on your computer through a local Bridge. It also supports OpenCode, Codex, Claude Code, Pi, OMP, and Hermes. Ordinary app-to-Bridge payloads are end-to-end encrypted; review diffs and respond to available permission requests where the selected assistant exposes them.
Trade-off Your computer must remain on; coding assistants, model providers, and optional hosted features retain their own data paths.
Best for Developers who want a focused mobile workflow across seven supported coding assistants and a documented relay boundary.
Read Sesori’s setup guide →