Skip to lesson
Exit
Context, tools & MCP1 / 2

2 min lesson

Scope one task

Think through this situation. "Agent must fix a failing checkout-total test. What do you attach?" Give the practical answer in plain words.

Step 1 of 2

Scope one task

Task: Fix the failing checkout total test.

Attach the failing test and the one pricing handler it calls. Nothing else.

Say why: the test defines done, the handler is where the fix lands.

  1. 1Pick one safe repo task and name the exact done signal.
  2. 2Attach the one item from the list that proves that signal, and nothing else.
  3. 3Start Agent, watch the tool rows, then interrupt or queue a follow-up if the run drifts.

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.
Check your scoping against the run: the tool rows show which files Agent actually read, Stop pauses a run that drifts, and a queued follow-up corrects it without a restart.

Practice next: Now run the practice: stop a live Agent run, queue the follow-up, and let the next step continue.

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