Choose the action that matches the problem
- Withdraw a message
- Available only before any recipient claims the eligible message. It removes the pending request through the product’s withdrawal path; it is not a way to interrupt a running Agent.
- Stop a Run
- Stops the selected attempt. Other teammates and waiting deliveries are separate. Check for a successor request before assuming the entire conversation is idle.
- Cancel a Task
- Ends a recorded responsibility. Inspect and stop any active execution separately when that is also your intent.
- Change Mission status
- Changes the board’s business state. It does not stop every Run, roll back files, merge a branch or clean the worktree.
Continue after an interruption
- Read the last Run state and last observed step. Check whether it was waiting, stopped, failed or left with an uncertain outcome.
- Inspect the actual modified files and any queued requests. Stop is not undo.
- Resolve the missing permission, account, network or product decision.
- Send a new, bounded follow-up: state what already exists, what remains and which files may change. Do not replay the whole request when it could repeat a side effect.
How to use it
- Open the execution panel, focus the active run, and use its Stop control when you want that run to stop.
- Wait for the recorded final state. Inspect the conversation and project files for changes made before the stop took effect.
- After an App, Agent, or network interruption, reopen the same conversation and inspect its run state before sending another request.
Different interruption cases
- Stop this run
- Focus the active run and use its Stop control. This targets that run, not every teammate or queued request.
- App or host closes
- Reopen the same conversation and inspect the recorded state before sending the same request again.
- Agent or network fails
- Read the error and last successful step. Correct authentication, connection or input before retrying.
Why inspection comes before retry
A stop or crash cannot undo file writes already completed. The public reply may also be missing even when earlier tool steps ran.
Look at the run, any files it touched and the pending queue. Then send a follow-up that says what is already done and what remains, rather than blindly repeating the entire task.