Start here
Run your first coding agent from Android
Your first run should prove the control loop, not the size of the task. Pick a small reversible change so you can see the prompt, progress, questions, tools, diff, and recovery surfaces in one pass.
Quick answer
The shortest useful version.
Ask the agent for a small documentation or test change, require it to explain the plan before editing, follow the live evidence, answer only expected prompts, and inspect every changed file before approving.
Step by step
Do this with confidence.
- 01
Choose a reversible task
Good first runs include clarifying a README section, adding one focused test, or explaining a module before proposing a patch.
- 02
Select an available provider
Use the readiness information FireCursor exposes. Cursor, Codex, and Claude have different setup and plan requirements; choose deliberately.
- 03
State the finish line
Tell the agent exactly what may change, what must remain untouched, and which verification command should pass.
- 04
Review before approval
Follow the transcript and tool events, answer questions, inspect the per-file diff, then approve or restore the checkpoint.
A useful first prompt
Try: ‘Read the relevant files first. Update only the setup paragraph in the README so it matches the current command. Show the proposed change and run the documentation check. Do not alter any other file.’
The exact task is less important than the boundaries. A clear scope makes FireCursor’s decisions, evidence, and undo path easy to understand.
What success looks like
- The correct provider starts without hidden setup work
- The agent stays inside the requested files
- Questions and sensitive tools pause for your input
- The final diff matches the requested outcome
- You know where to resume or recover the session