Use diffs, checks, and checkpoints as complementary evidence rather than automatic acceptance.
Coding & development · Documented · Documentation checked 2026-10-04
Cursor editor agents and Cloud Agents; Grok Bot has a separate shared-computer boundary.
Installed client, subscription, organization settings, repository access, and cloud environment determine capabilities.
The worked example is illustrative and has not been tested in a signed-in product account.
What it does and how it connects
Use diffs, checks, and checkpoints as complementary evidence rather than automatic acceptance.
Diffs show the change; tests show selected behavior; checkpoints can restore captured agent file changes. These answer different questions. Restoring a checkpoint does not restore every manual edit or roll back an external action. Git history and service-level recovery remain important.
Walkthrough
Use the product named in the access panel. The steps below combine documented controls with the editorial example.
- Inspect the current Git diff and preserve valuable human work.
- Ask for a review focused on the concrete change and acceptance criteria.
- Reproduce important findings and run appropriate checks.
- Use a checkpoint only after understanding its scope; confirm the resulting files and Git state.
Worked example
A sample agent breaks a menu while fixing a layout. Review the exact files and decide whether to restore the agent change or patch the specific regression. Do not restore blindly over unrelated edits.
Review the current navigation changes against the original menu behavior. Identify reproducible regressions, changed destinations, and missing checks. Do not edit yet. Explain which files would need restoration and what a checkpoint would not recover.
Inspect and verify the result
Compare before / after behavior and the actual diff. Inspect Git state after a restoration. Verify external side effects separately from local files; a restored file does not undo a sent message or service update.
Limits and troubleshooting
Checkpoints are limited to captured agent changes and are not durable version control. Tests can miss untested behavior, and reviews can produce false alarms. Keep a small reversible scope and a human-controlled merge process.
Data, permissions, and actions
Review context can include code and logs. Avoid exposing secrets when sharing them. Restoration affects file state, while connected-service permissions and records follow their own lifecycle and recovery rules.
Related reading
Agent, codebase context, and checkpoints
Connect instructions, a model, and tools into a local development loop you can inspect.
A local UI repair with deliberate recovery
Fix a sample UI problem while preserving unrelated work.
A cloud change with source and environment review
Run a scoped remote task and hand off tested branches or pull requests.
Evaluations: does the system do the job?
Create representative tests for quality, tool behavior, refusal, escalation, and the effects of a change.
Sources and verification
Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.
Agent fundamentals and checkpoints · Cursor
Agent security and approvals · Cursor
Cloud Agents and environments · Cursor