Cursor · Workflows

Agent loop

Plan first, use checkpoints, redirect Agent while it works, choose a Run Mode, and run Agent Review before you commit.

The Cursor agent loop

Three points where you can step in

You can shape a run before, during and after it. Before: Plan mode and your Run Mode. During: queue a message, steer it, or click Stop. After: read the diff, restore a checkpoint or run Agent Review. Most lost time comes from only stepping in at the end, when a wrong assumption has already spread.

Give it a finish line

An agent needs a way to know it's done. A command that passes is better than a description, such as "npm test passes and the list excludes deleted orders". Cursor's course says if the agent can't verify its output, you end up spending more time making corrections. For a long objective that spans many turns, use /goal.

Frequently asked
How do I use Plan mode in Cursor?

Open Agent, press Shift+Tab until the mode shows Plan, and describe your task. Agent researches and asks questions, then produces a plan you can edit. Click Build when you're happy with it.

Can I send a message while Cursor's agent is working?

Yes. Enter queues it for after the current task. Cmd+Enter or Ctrl+Enter sends it immediately. Steering with Send now delivers it at the agent's next tool call where available.

What is a checkpoint in Cursor?

It's a local snapshot of modified files that Agent makes automatically before significant changes. Restoring one reverts files but keeps the conversation. Checkpoints are separate from Git, so commit anything you want to keep.

Where are Cursor plans saved?

In your home directory by default. Click Save to workspace to move a plan into your project for future reference and team sharing.