Choose an agent
Use a Cursor agent from Android
FireCursor connects to Cursor’s supported agent surface so the agent keeps operating in the desktop workspace while Android exposes the controls the running session advertises.
Quick answer
The shortest useful version.
Pair the workspace, choose Cursor, select an available mode or model, attach precise context with @ or project commands with /, then supervise questions, tools, and the final diff.
Step by step
Do this with confidence.
- 01
Check Cursor readiness
Confirm Cursor is signed in and the project is open. FireCursor surfaces provider readiness rather than assuming every runtime is configured.
- 02
Set the run controls
Choose from the modes, models, effort, context, thought-level, and fast controls the active Cursor interface makes available.
- 03
Add project-native context
Use / to discover project commands and @ to attach a workspace file to the next message. Keep each prompt scoped.
- 04
Close the loop
Watch execution evidence, answer questions, decide on sensitive tools, and inspect the file changes before approving.
Why this beats a generic mobile chat
The session remains project-aware. FireCursor can surface project commands, files, rules, agent state, tool decisions, and diffs instead of reducing the interaction to text messages.
Controls remain provider-aware: FireCursor should show what the connected Cursor runtime actually supports, not fabricate a least-common-denominator interface.
Best task shapes
- Focused implementation with a clear test command
- Repository explanation followed by a proposed patch
- Review and repair of a small failing test
- Documentation synchronized to shipping behavior
- A checkpointed change that is easy to inspect on mobile