Start here

Pair FireCursor on Android with Cursor

Pairing joins one Android device to the remote-control session started by the Cursor extension. The pairing details identify a temporary TLS tunnel and prove possession of the random session token.

By FireCursor product teamFor New FireCursor usersOutcome Connect the right phone to the right workspace
LinkedInRedditEmail
FireCursor Android launch screen with local and cloud agent options
Current FireCursor Android product interface

Quick answer

The shortest useful version.

Open the correct workspace in Cursor, run Start Remote Control, scan the QR code in FireCursor, confirm the displayed project, and stop the desktop session when the remote-control window is no longer needed.

Step by step

Do this with confidence.

  1. 01

    Prepare the workspace

    Open the repository or workspace you intend to control. Confirm its name and trust state before exposing a remote session.

  2. 02

    Start remote control

    Run ‘FireCursor: Start Remote Control’ from Cursor. The extension starts its local bridge and presents the pairing details.

  3. 03

    Scan from Android

    In FireCursor, choose the pairing action and scan the QR code. If camera access is unavailable, use the manual details shown by the extension.

  4. 04

    Confirm project identity

    Check that Android shows the expected project and provider readiness before launching an agent. Stop and repeat pairing if anything does not match.

What travels across the connection

Remote traffic uses TLS through a temporary Cloudflare quick tunnel and is gated by a random pairing token. The connection carries supported agent control events and project-scoped evidence; local execution remains on the paired computer.

Treat the QR code and manual pairing values like a short-lived password. Do not post them in chat, screenshots, or issue reports.

Pairing hygiene

  • Pair in a private setting
  • Verify the workspace name on both screens
  • Do not reuse screenshots of pairing data
  • Stop remote control after the session
  • Pair again rather than guessing when a token has expired

Keep moving

See all thirty