stop

To pause a background agent and save progress, use the stop functionality to halt execution, detect the current state, capture session insights, and update plan documentation and logs for later resumption.

Capturing session insights before pausing manual work involves stopping the current plan, which interactively prompts for confirmation, saves detailed notes, and updates logs to preserve your current progress.

Stopping a running autonomous agent without losing work requires halting the execution to trigger state detection, saving captured insights, and updating plan documentation so the session can be resumed later.

Resuming a paused plan after stopping background execution is fully supported; you can interactively restart the plan or run it in the background using dedicated resume commands to continue your work.

Stopping a background agent requires user interaction and task execution tools to manage plan states, detect execution conditions, and handle user confirmations for safely pausing and saving the session.

You should pause plan management to switch to an urgent task whenever you need to gracefully halt ongoing work, ensuring that execution state is detected, progress is saved, and insights are captured for later resumption.