Control and review
Review agent code diffs on Android
Mobile review works when it is structured around decisions. FireCursor exposes per-file changes and session evidence so you can verify scope, behavior, and unexpected edits without scanning a remote desktop.
Quick answer
The shortest useful version.
Start with the changed-file list, flag any file outside scope, read additions and deletions in context, compare the diff with the verification output, then approve or restore the checkpoint.
Step by step
Do this with confidence.
- 01
Check the file inventory
Unexpected lockfiles, configuration, generated output, or unrelated source files are immediate review signals.
- 02
Read for intent
Confirm each change contributes to the requested outcome and preserves surrounding contracts.
- 03
Match evidence to risk
A copy edit may need a focused check; authentication, release, or data changes deserve stronger tests and desktop review.
- 04
Choose keep or recover
Approve when scope and verification are convincing. Restore the checkpoint when the run drifted or evidence is insufficient.
Review order that fits a phone
- Files changed
- High-risk configuration and dependencies
- Public API or data-shape changes
- Tests and verification output
- Copy, comments, and generated files
What a diff cannot prove
A clean diff does not prove the app boots, the UI renders correctly, a deployment succeeded, or an external provider accepted the request. Use FireCursor’s evidence as a decision aid and run the verification appropriate to the change.
For a large or security-sensitive patch, use Android to triage and defer final approval until a full desktop review.