Work with confidence
Troubleshoot pairing, tunnels, and reconnection
A failed run can originate in five different layers: the extension, temporary tunnel, pairing token, Android network, or selected provider. Diagnose them in that order instead of reinstalling everything.
Quick answer
The shortest useful version.
Confirm the Start Remote Control command is active, generate fresh pairing details, test Android network access, verify project identity, and only then troubleshoot the selected agent provider.
Step by step
Do this with confidence.
- 01
Check the desktop bridge
Keep Cursor open, verify the FireCursor extension is enabled, and run Start Remote Control in the intended workspace.
- 02
Create fresh pairing details
Do not reuse an old QR screenshot or token. Stop the prior session and generate a new temporary tunnel.
- 03
Test the Android path
Switch between Wi-Fi and cellular if policy allows, disable network filters temporarily for diagnosis, and check the device clock.
- 04
Separate provider errors
If pairing succeeds but an agent will not start, inspect provider authentication, plan, CLI health, and runtime readiness.
Use the symptom to choose the layer
- No FireCursor command: extension install or reload issue
- QR cannot connect: tunnel, network, or expired token
- Wrong project: workspace or stale pairing state
- Connected but provider unavailable: provider setup or authentication
- Messages delayed after a drop: outbox and session reconciliation
What to capture for support
Record the app and extension versions, the step that fails, the exact non-secret error text, Android device and OS family, network type, and whether a fresh session changes the result.
Never include pairing tokens, API keys, private repository content, or uncropped screenshots with secrets.