Stopping an agent

Stop any reply the moment it heads the wrong way. Files are never left half-written.

Stop a reply

While an agent is replying, the send button becomes Stop — it’s in ⌘K too. The reply ends straight away and is saved with what it wrote so far.

Stopping takes effect between tool calls, so a file is never left half-written, and no typecheck, test run, commit or fix round starts after it.

Files it already changed stay as they are. Review or revert them in the reply, or restore the checkpoint from before it — see Checkpoints and undo.

Pause in the pipeline stops the step that’s running straight away, instead of waiting for it to finish.

A stopped request still counts in the cost meter, as an estimate, because the provider bills it.