Start here
What is FireCursor? Your coding agents, without the desk
FireCursor is an Android control plane for coding agents. The work stays with the supported runtime on your computer—or in Cursor Cloud—while your phone becomes the focused surface for direction, evidence, approvals, and review.
Quick answer
The shortest useful version.
Use FireCursor when an agent should keep working after you leave the keyboard, but you still want an explicit say over prompts, tools, questions, diffs, and recovery.
Step by step
Do this with confidence.
- 01
Pair the two surfaces
Install the Cursor extension and Android app, start remote control on the computer, then scan the QR code or enter the pairing details.
- 02
Choose the runtime
Select Cursor, Codex, Claude, or a Cursor Cloud workflow based on authentication, availability, and the work you need done.
- 03
Stay in the control loop
Send instructions, follow execution evidence, answer questions, and make sensitive tool decisions from the Android surface.
- 04
Review the result
Inspect file-level changes and session state before approving the work or restoring the checkpoint.
A controller, not a second coding environment
FireCursor does not move your repository into a phone editor. Local runs continue through the supported desktop provider interface in the trusted workspace. Android carries the conversation and the decision surfaces that matter when you are away.
That separation is the useful part: the computer keeps its files, credentials, tools, and compute, while the phone gives you a compact way to supervise progress.
Why the experience feels different
Remote desktop products reproduce an entire monitor. FireCursor presents the agent workflow itself: provider readiness, the active task, questions, tool approvals, diffs, history, and project evidence.
- One adaptive interface for phone, tablet, and foldable layouts
- Provider-aware controls instead of one generic chat box
- Local and Cursor Cloud paths without pretending they have identical security boundaries