A conversation that can continue
A mission keeps the objective, conversation, selected settings and recorded work together across turns. A turn is one period of agent work. When it ends, the mission can remain idle until you send another message. An idle mission is not a certification that the broader objective succeeded.
Use a new mission for a separate objective. Keep a follow-up in the existing mission when its prior decisions and context are still relevant.
Guide work in progress
Send guidance while a turn is running. Agents that support live steering can receive it during that turn; other paths queue a follow-up. Check the message's delivery state instead of assuming it took effect immediately. Queued follow-ups appear as upcoming work.
Use the stop control to interrupt current work. Interruption does not undo completed file edits or external actions. Inspect the last reported result before asking for a retry, especially after a push, deployment or other outward effect.
Answer questions and approvals
A question requests information. Select the offered answer or enter custom text when that question allows it. An approval authorizes the particular action shown. Review the command, affected files or requested operation before deciding.
If a request expires or changes, use the current request in the mission. An earlier approval does not authorize a changed action.
Continue with another agent
Changing agents after a mission has history can require your consent to share that history with the destination provider. Read the destination and account shown. The mission's Shared history action lists grants. Revoking a grant stops future replay; it cannot recall information already sent.
Archive work
Choose Archive mission from the mission's actions menu to remove it from the active list. The conversation and recorded history are preserved. Use Reopen last closed (⇧⌘T) to restore the most recently closed item.