Stop, Pause and Restore AI Agents
Use the control that matches how long you want work to stop. Stopping a run, pausing an agent, and deleting an agent have different effects.
| Action | Effect | When to use it |
|---|---|---|
| Stop current work | Requests that the current agent loop stop and cancels associated browser work | Interrupt a run that is taking the wrong direction |
| Pause the agent | Sets the agent inactive so it does not start normal processing while paused | Suspend an ongoing responsibility |
| Disable or remove a schedule | Changes that scheduled trigger | End a reminder while keeping the agent available for other work |
| Delete the agent | Archives it and removes it from active lists | Retire an agent from everyday use |
Interrupt or pause work
Use Stop in chat when it is available for running work. Stopping is cooperative: an action already sent to an external service may finish. Check the timeline and the external system before repeating or trying to undo a write. Stop does not undo messages, purchases, or edits already made, and it does not disable future schedules.
For a longer suspension, open the agent's Settings, turn off its active control, and save when prompted. Pause also does not reverse completed work. Review pending approvals and any queued messages before reactivating an agent, since retained work may still need attention.
To stop just one recurring task, ask the agent to list its schedules and disable the named entry. See Schedules And Reminders.
Retire an agent
Before using Delete agent in Settings, decide whether you need a portable export, and review outside systems that depend on its messages or webhooks. Deletion archives the agent in the current implementation; historical records remain subject to retention policies. Archiving is not a backup or a way to preserve files indefinitely.
The settings page and deletion confirmation explain archiving and link to the API options for recovery. Restore is available through the public API; there is currently no corresponding restore control in the regular settings screen.
Restore an archived agent
An authorized owner or administrator can use the archive and restore API options to list archived agents and restore the selected ID. The recovery endpoints are GET /api/v1/agents/archived/ and POST /api/v1/agents/{id}/restore/.
Restoration leaves the agent inactive so you can review it before work resumes. A duplicate active name in the same workspace blocks restore with a conflict; resolve that name conflict before retrying. Communication endpoints are reclaimed only when available, so verify the resulting addresses after restoration. Review restored schedule settings, contacts, integrations, and pending work before switching the agent active again.
Restoring an agent does not recover content that retention cleanup already removed, recreate revoked provider access, or undo actions in external systems. If the archive is unavailable, check the owning workspace and permissions with its administrator.