Skip to lesson
Exit
Checkpoints, queued messages and run control1 / 3

2 min lesson

When an Agent run drifts

Stop a run before another wrong tool call, send a narrower request and review the diff.

Step 1 of 3

Agent is about to edit outside the accepted files. Send now reaches Agent at its next tool call, so the call already running can still finish. Stop is the only control that prevents more tool calls, and queued work waits for the active task.

Stop, queue, continue

0:34 · narrated
Read this demo as text
  1. See that? The run is live, and the mic turned into a black square. That square is Stop. Hit it when you need to steer before this goes further.
  2. Now type the follow-up as its own message and queue it. It waits for the current step. You redirected the run without throwing the context away.
  3. Step finishes... and your queued follow-up is next. Interrupt, steer, keep going. No restart.
Queue a follow-up that can wait. For a boundary correction, use Send now, or Stop and send a narrower request.

Practice next: Run the demo's safe queued case, then apply the boundary rule: send an urgent correction now or Stop before another tool call.

Simulated Cursor 3.12 (macOS, light) — beta educational reconstruction, not the real product.