Guide
How to use Cursor from your phone in 2026
This guide reflects first-party product pages reviewed on August 25, 2026. Cursor now has a native iOS app and an Android PWA for Cloud Agents, while several independent tools connect mobile clients to Cursor on your own machine. Here is the current picture and the architectural tradeoff behind each route.
The 6 practical options
Option 1
Cursor for iOS and Android PWA
Cursor's native iOS app runs Cloud Agents and, on supported paid plans, can use Remote Control for a Git-backed workspace on your computer. On Android, Cursor documents installing cursor.com/agents as a PWA for the Cloud Agents workflow; it has not released a native Android app. Cloud Agents run in Cursor infrastructure, while Remote Control keeps tool calls on an awake, online computer and moves the agent loop to Cursor's cloud.
Best for Cursor users who want the official experience and are comfortable with Cursor Cloud Agents.
Visit →Option 2
Paseo
Free, open-source orchestrator with native iOS and Android apps plus desktop, web, and CLI clients. Paseo runs Cursor CLI on your machine alongside 38 other documented agents. Mobile clients connect directly or through an optional end-to-end encrypted relay, and the local daemon remains the execution endpoint.
Best for Developers who want broad open-source agent coverage, self-hosting options, and several client surfaces.
Visit →Option 3
Orca
Free, MIT-licensed Agent Development Environment for running Cursor CLI and other terminal agents in isolated worktrees. Its iOS and Android companion pairs to Orca desktop for agent status, terminal or chat replies, file browsing, source-control review, and commits. The desktop stays the source of truth and must remain reachable.
Best for Developers who want a desktop-first worktree IDE with a capable phone companion.
Visit →Option 4
T3 Code
Free, MIT-licensed desktop and web control plane with iOS and Android companions. Cursor support uses the Cursor CLI on the machine running T3 Code and is opt-in under provider settings. Remote access can use LAN, Tailscale, SSH-managed environments, custom HTTPS, or T3 Connect.
Best for Developers who want a forkable desktop control plane and multiple remote-connection choices.
Visit →Option 5
CodeAgent Mobile
Native iOS and Android app plus a web dashboard. It works through IDE plugins and a CLI and explicitly lists Cursor among a broad range of supported coding tools. Prompts and output pass through its backend relay, so review its current architecture and plan limits before choosing it.
Best for Teams already using its supported IDE plugins or developers prioritizing integration breadth.
Visit →Option 6
Sesori
Mobile cockpit for OpenCode, Codex, Cursor, Claude Code, Pi, OMP, and Hermes on iOS and Android. The Bridge runs beside Cursor on your computer, while ordinary session traffic crosses an end-to-end encrypted relay. Review diffs, approve permissions, use voice, queue messages, run parallel sessions, and receive push notifications. Your machine must remain running.
Best for Developers who want a focused mobile workflow across seven supported harnesses and a documented relay boundary.
Learn more →